# CVE-2025-46675: In NASA CryptoLib before 1.3.2, the key state is not checked before use, potentially leading to spacecraft hijacking.


- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-m25x-4j5x-r9v6

## What is CVE-2025-46675?

CVE-2025-46675 is a low-severity vulnerability in NASA CryptoLib, published on 27 Apr 2025. 

### Official description

In NASA CryptoLib before 1.3.2, the key state is not checked before use, potentially leading to spacecraft hijacking.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

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

It affects 1 product.


Products: Nasa Cryptolib.

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

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

## Is CVE-2025-46675 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46675 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-46675 and fix it if it is affected.

What it is: CVE-2025-46675 is a low-severity vulnerability in NASA CryptoLib, published on 27 Apr 2025. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46675 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-46675/ (Markdown: https://insights.sbomify.com/CVE-2025-46675/index.md)
```

## Sources

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

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