# CVE-2025-64096: CryptoLib vulnerable to Stack Buffer Overflow in Crypto_Key_Update due to missing TLV length check

> A remote attacker can trigger a stack buffer overflow in CryptoLib via a spoofed TLV length, potentially leading to code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2025
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-w6c3-pxvr-6m6j

## What is CVE-2025-64096?

CVE-2025-64096 is a high-severity memory corruption vulnerability in nasa CryptoLib, published on 30 Oct 2025. Any signed-in user can exploit it over the network, 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 1.4.2, there is a missing bounds check in Crypto_Key_update() (crypto_key_mgmt.c) which allows a remote attacker to trigger a stack-based buffer overflow by supplying a TLV packet with a spoofed length field. The function calculates the number of keys from an attacker-controlled field (pdu_len), which may exceed the static array size (kblk[98]), leading to an out-of-bounds write and potential memory corruption. This vulnerability is fixed in 1.4.2.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-64096?

It affects 1 product.


Products: Nasa Cryptolib.

## How do I fix CVE-2025-64096?

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

## Is CVE-2025-64096 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64096 exists.

## Other vulnerabilities in nasa CryptoLib

- [CVE-2025-30216](https://insights.sbomify.com/CVE-2025-30216/): CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length (critical 9.4)
- [CVE-2025-30356](https://insights.sbomify.com/CVE-2025-30356/): Heap Buffer Overflow via Incomplete Length Check in `Crypto_TC_ApplySecurity` (critical 9.3)
- [CVE-2025-29909](https://insights.sbomify.com/CVE-2025-29909/): CryptoLib's Crypto_TC_ApplySecurity() Has a Heap Buffer Overflow Vulnerability (high 8.9)
- [CVE-2025-29911](https://insights.sbomify.com/CVE-2025-29911/): CryptoLib Has Heap Buffer Overflow in Crypto_AOS_ProcessSecurity Function (high 8.9)
- [CVE-2025-29912](https://insights.sbomify.com/CVE-2025-29912/): CryptoLib Has Heap Buffer Overflow Due to Unsigned Integer Underflow in Crypto_TC_ProcessSecurity (high 8.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64096 and fix it if it is affected.

What it is: CVE-2025-64096 is a high-severity memory corruption vulnerability in nasa CryptoLib, published on 30 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64096 exists.

Affected product: nasa CryptoLib. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64096/ (Markdown: https://insights.sbomify.com/CVE-2025-64096/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64096
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64096
- OSV: https://osv.dev/vulnerability/CVE-2025-64096

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64096/
Summaries are generated and may contain mistakes; the official description above is the record.