CVE-2025-46675 json
In NASA CryptoLib before 1.3.2, the key state is not checked before use, potentially leading to spacecraft hijacking.
published 2025-04-27 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-12472
- cvss
- 3.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
In NASA CryptoLib before 1.3.2, the key state is not checked before use, potentially leading to spacecraft hijacking.
Patch / fix
- NASA CryptoLib 1.3.2
- github.com/nasa/CryptoLib/compare/v1.3.1...v1.3.2 patch
- github.com/nasa/CryptoLib#358 pull request
- github.com/nasa/CryptoLib#359 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securitybynature.fr https://securitybynature.fr/post/hacking-cryptolib/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N |
| NVD | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L |
Affected products
- NASA CryptoLib
Classification
- Weakness
-
- CWE-913 Improper Control of Dynamically-Managed Code Resources
References
-
github.com
/nasa/CryptoLib/pull/358
issue-tracking, patch
-
github.com
/nasa/CryptoLib/pull/359
issue-tracking, patch
-
github.com
/nasa/CryptoLib/compare/v1.3.1...v1.3.2
patch
-
securitybynature.fr
/post/hacking-cryptolib/
exploit, third-party-advisory
Sources
- CVE List CVE-2025-46675
- NVD CVE-2025-46675
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.