Process crash via unbounded KDF memory allocation
Published Aug 27, 2026 · Updated Aug 27, 2026
Uncontrolled resource consumption in OpenSSL Encrypt before 1.4.9 allows attackers to crash the process via crafted encrypted files. The encrypted-file and keystore-header parsers accept attacker-declared Argon2, scrypt, or Balloon cost values and allocate memory without a ceiling. Processing an attacker-controlled file requires no authentication and can exhaust host memory before cryptographic verification.
Summary
What happened
Uncontrolled resource consumption in OpenSSL Encrypt before 1.4.9 allows attackers to crash the process via crafted encrypted files. The encrypted-file and keystore-header parsers accept attacker-declared Argon2, scrypt, or Balloon cost values and allocate memory without a ceiling. Processing an attacker-controlled file requires no authentication and can exhaust host memory before cryptographic verification.
The record
- CVE
- CVE-2026-81721
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=0 <1.4.9
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.
Public exploit references
No public exploit references are available in this record.
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