Memory corruption via incorrect signed-attribute capacity
Published Mar 19, 2026 · Updated Mar 19, 2026
Stack buffer overflow in wolfSSL 5.5.0 through 5.8.4 allows attackers to corrupt memory through custom PKCS7 signed attributes. wc_PKCS7_BuildSignedAttributes passes the current attribute count, rather than remaining signedAttribs[7] capacity, to EncodeAttributes. The condition requires an application to let untrusted input control more than seven attributes; WOLFSSL_SMALL_STACK builds corrupt heap memory.
Summary
What happened
Stack buffer overflow in wolfSSL 5.5.0 through 5.8.4 allows attackers to corrupt memory through custom PKCS7 signed attributes. wc_PKCS7_BuildSignedAttributes passes the current attribute count, rather than remaining signedAttribs[7] capacity, to EncodeAttributes. The condition requires an application to let untrusted input control more than seven attributes; WOLFSSL_SMALL_STACK builds corrupt heap memory.
The record
- CVE
- CVE-2026-0819
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- wolfSSL
- Product
- wolfSSL
- Classifications
- CWE-787, CWE-121
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 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=5.5.0 <5.9.0
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.
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