Resource exhaustion via unreleased encryption buffers
Published Jan 10, 2026 · Updated Jan 10, 2026
A memory leak in CryptoLib's KMC encryption interface before 1.4.3 allows remote attackers to exhaust memory through sustained encryption traffic. The cryptography_encrypt() function allocates roughly 400 to 500 bytes across HTTP-request and JSON-processing buffers per call but frees none on success or error paths. Reachability requires the KMC cryptography backend and repeated encryption calls; accumulation degrades performance and can end in an out-of-memory service interruption.
Summary
What happened
A memory leak in CryptoLib's KMC encryption interface before 1.4.3 allows remote attackers to exhaust memory through sustained encryption traffic. The cryptography_encrypt() function allocates roughly 400 to 500 bytes across HTTP-request and JSON-processing buffers per call but frees none on success or error paths. Reachability requires the KMC cryptography backend and repeated encryption calls; accumulation degrades performance and can end in an out-of-memory service interruption.
The record
- CVE
- CVE-2026-22024
- Published
- Jan 10, 2026
- Updated
- Jan 10, 2026
- Vendor
- NASA AMMOS
- Product
- CryptoLib
- Classifications
- CWE-401, T1499
- 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?
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 encrypt memory-leak sanitizer PoCproof 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