Memory exhaustion via unfreed HTTP-error buffers
Published Jan 10, 2026 · Updated Jan 10, 2026
Memory leak in the KMC client in NASA AMMOS CryptoLib before 1.4.3 allows remote attackers controlling KMC responses to exhaust memory. On a non-200 response, cryptography_encrypt(), cryptography_decrypt(), and cryptography_authenticate() return before freeing HTTP and request buffers. Exploitation requires control of the KMC server or a man-in-the-middle position and repeated failed requests, which can interrupt the host process as memory is depleted.
Summary
What happened
Memory leak in the KMC client in NASA AMMOS CryptoLib before 1.4.3 allows remote attackers controlling KMC responses to exhaust memory. On a non-200 response, cryptography_encrypt(), cryptography_decrypt(), and cryptography_authenticate() return before freeing HTTP and request buffers. Exploitation requires control of the KMC server or a man-in-the-middle position and repeated failed requests, which can interrupt the host process as memory is depleted.
The record
- CVE
- CVE-2026-22025
- Published
- Jan 10, 2026
- Updated
- Jan 10, 2026
- Vendor
- NASA AMMOS
- Product
- CryptoLib
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2026CVE publishedPublication date reported by the CVE source.
- Jan 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- KMC HTTP-error memory-leak proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo