● High · CVSS 8.2

How to Fix CVE-2026-21900: Path Traversal in CryptoLib

Q: Is CVE-2026-21900 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-21900?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for CryptoLib run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-25947: SQL Injection in worklenz — SQL Injection in worklenz
How to Fix CVE-2026-21002: Improper Verification of Cryptographic Signature in Galaxy Store — Improper Verification of Cryptographic Signature in Galaxy Store
How to Fix CVE-2026-4208: Authentication Bypass in extension "E-Mail MFA Provider" (mfa_email) , Authentication Bypass in extension "E-Mail MFA Provider" (mfa_email)
How to Fix CVE-2026-2148: Information Disclosure in AC21 , Information Disclosure in AC21
How to Fix CVE-2026-20883: Access Control Bypass in Gitea Open Source Git Server , Access Control Bypass in Gitea Open Source Git Server

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 8.2 - High
Actively exploited?	Not currently listed in CISA KEV
Affected	< 1.4.3
Fixed in	version
Type (CWE)	CWE-125: Out-of-bounds Read

What is CVE-2026-21900?

CVE-2026-21900 is a path traversal flaw in CryptoLib. The product fails to canonicalize or restrict file paths supplied by a remote caller, so .. sequences or absolute paths reach restricted parts of the filesystem. Vendor description: CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. Prior to version 1.4.3, an out-of-bounds heap read vulnerability in cryptography_encrypt() occurs when parsing JSON metadata from KMC server responses.

Why this CVE matters

Path traversal flaws look low-impact on paper but routinely chain into full compromise. An attacker who can read arbitrary files often pulls configuration secrets, session databases, or private keys, and many traversal bugs also allow writes that drop a webshell into the document root.

For deployments of CryptoLib that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

CryptoLib: < 1.4.3

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open CryptoLib's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-21900

Read the vendor advisory in full: https://github.com/nasa/CryptoLib/security/advisories/GHSA-4g6v-36fv-qcvw
Upgrade CryptoLib to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Ubuntu / Debian

_Verify the exact patched build against the vendor advisory: https://github.com/nasa/CryptoLib/security/advisories/GHSA-4g6v-36fv-qcvw_


sudo apt-get update
sudo apt-get install --only-upgrade cryptolib
dpkg -s cryptolib | grep -i version

RHEL / Rocky / AlmaLinux / Fedora


sudo dnf upgrade --refresh cryptolib -y
rpm -q cryptolib

openSUSE


sudo zypper refresh
sudo zypper update cryptolib
rpm -q cryptolib

Bash detect / upgrade / verify runner (Linux)

_Verify the exact patched build against the vendor advisory: https://github.com/nasa/CryptoLib/security/advisories/GHSA-4g6v-36fv-qcvw_


#!/usr/bin/env bash
# CVE-2026-21900 remediation runner. Re-runnable; exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-21900-fix.log; }

PKG="cryptolib"
TARGET_VERSION="see vendor advisory"

log "Detect: reading current $PKG version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' "$PKG" 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' "$PKG" 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current (target per advisory: $TARGET_VERSION)"

log "Backup: snapshotting /etc/$PKG if present"
backup="/var/backups/cve-2026-21900-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d "/etc/$PKG" ] && cp -a "/etc/$PKG" "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade "$PKG"
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y "$PKG"
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y "$PKG"
fi

log "Verify: re-reading $PKG version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' "$PKG")
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' "$PKG")
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: $PKG upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

Verify the fix landed


# 1. Confirm the running version matches the patched build
#    (target per advisory: see vendor advisory)
#    Use the platform-specific version probe shown above.

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    Rapid7, OpenVAS). The scanner should no longer flag CVE-2026-21900.

# 3. Inspect service and kernel logs for crash-loops or rollback events
journalctl --since "10 minutes ago" | grep -iE 'error|fail|panic'
dmesg --since "10 minutes ago" | tail -50

If you cannot patch immediately

Block requests containing ../, ..%2f, or absolute path prefixes at a reverse proxy. Restrict access to the affected endpoint to trusted networks. Apply the patched build as the real fix.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-21900.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-21900 being exploited in the wild?