Memory disclosure via unchecked callback-returned lengths
Published Apr 24, 2026 · Updated Apr 24, 2026
Buffer over-read in the openssl Rust crate 0.9.24 through 0.10.77 allows remote attackers to receive adjacent process memory during TLS exchanges. Its PSK and cookie-generation FFI trampolines trust a callback's returned usize and tell OpenSSL to serialize that many bytes without bounding it to the supplied slice. Applications expose memory only when an affected callback returns an oversized length and a remote peer initiates the corresponding TLS or DTLS exchange.
Summary
What happened
Buffer over-read in the openssl Rust crate 0.9.24 through 0.10.77 allows remote attackers to receive adjacent process memory during TLS exchanges. Its PSK and cookie-generation FFI trampolines trust a callback's returned usize and tell OpenSSL to serialize that many bytes without bounding it to the supplied slice. Applications expose memory only when an affected callback returns an oversized length and a remote peer initiates the corresponding TLS or DTLS exchange.
The record
- CVE
- CVE-2026-41898
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- rust-openssl
- Product
- openssl
- Classifications
- CWE-126, CWE-130, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 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.9.24, < 0.10.78
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
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