CVE-2026-21897 CryptoLib Has Out-of-Bounds Write in Crypto_Config_Add_Gvcid_Managed_Parameters

High 7.3 Published Updated

An out-of-bounds write in CryptoLib allows attackers to corrupt memory and potentially execute arbitrary code or escalate privileges in spacecraft communications.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-21897?

CVE-2026-21897 is a high-severity memory corruption vulnerability in nasa CryptoLib, published on 10 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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, the Crypto_Config_Add_Gvcid_Managed_Parameters function only checks whether gvcid_counter > GVCID_MAN_PARAM_SIZE. As a result, it allows up to the 251st entry, which causes a write past the end of the array, overwriting gvcid_counter located immediately after gvcid_managed_parameters_array[250]. This leads to an out-of-bounds write, and the overwritten gvcid_counter may become an arbitrary value, potentially affecting the parameter lookup/registration logic that relies on it. This issue has been patched in version 1.4.3.

Weakness: CWE-787

Which versions are affected by CVE-2026-21897?

It affects 1 product.

Products include Nasa Cryptolib.

How do I fix CVE-2026-21897?

No fix has been published for CVE-2026-21897 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-21897 being exploited?

There is no known exploitation of CVE-2026-21897 in the wild and no public exploit code.

Sources

Also known as GHSA-9x7j-gx23-7m5r.

Is CVE-2026-21897 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free