Project Subscriptions
No data.
No advisories yet.
Solution
No solution given by the vendor.
Workaround
Disabling CRL processing is the only effective workaround for this issue. Preventing the overflow by validating the CRL number length requires source code modification and therefore should be considered a fix rather than a workaround.
Thu, 19 Mar 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 19 Mar 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsing CRL numbers: a heap-based buffer overflow could occur when improperly storing the CRL number as a hexadecimal string, and a stack-based overflow for sufficiently sized CRL numbers. With appropriately crafted CRLs, either of these out of bound writes could be triggered. Note this only affects builds that specifically enable CRL support, and the user would need to load a CRL from an untrusted source. | |
| Title | Buffer overflow in CRL number parsing in wolfSSL | |
| Weaknesses | CWE-122 CWE-787 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: wolfSSL
Published:
Updated: 2026-03-19T18:00:53.844Z
Reserved: 2026-03-04T18:42:04.494Z
Link: CVE-2026-3548
Updated: 2026-03-19T18:00:45.496Z
Status : Received
Published: 2026-03-19T18:16:22.953
Modified: 2026-03-19T18:16:22.953
Link: CVE-2026-3548
No data.
OpenCVE Enrichment
No data.