Memory corruption via oversized X.509 dates
Published Apr 9, 2026 · Updated Apr 9, 2026
Heap-based buffer overflow in wolfSSL before 5.9.1 allows attackers to corrupt memory through crafted X.509 certificate dates. CopyDecodedToX509 accepts date lengths up to 32 bytes, but wolfSSL_X509_notBefore and wolfSSL_X509_notAfter copy them at offset two into 32-byte buffers without reserving those two bytes. Exposure requires an application to call either compatibility API directly on attacker-controlled certificate data; wolfSSL TLS and certificate verification paths are unaffected.
Summary
What happened
Heap-based buffer overflow in wolfSSL before 5.9.1 allows attackers to corrupt memory through crafted X.509 certificate dates. CopyDecodedToX509 accepts date lengths up to 32 bytes, but wolfSSL_X509_notBefore and wolfSSL_X509_notAfter copy them at offset two into 32-byte buffers without reserving those two bytes. Exposure requires an application to call either compatibility API directly on attacker-controlled certificate data; wolfSSL TLS and certificate verification paths are unaffected.
The record
- CVE
- CVE-2026-5448
- Published
- Apr 9, 2026
- Updated
- Apr 9, 2026
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- CWE-122
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2026CVE publishedPublication date reported by the CVE source.
- Apr 9, 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 <5.9.1
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