CVE-2026-3548
published 2026-03-19CVE-2026-3548: Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsing CRL numbers: a heap-based buffer overflow could occur when improperly…
PriorityP353critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.47%
37.7th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | wolfssl | < wolfssl 5.9.0-0.1 (forky) | wolfssl 5.9.0-0.1 (forky) |
| msrc | azl3_mariadb_10.11.16-1_on_azure_linux_3.0 | — | — |
| msrc | cbl2_mariadb_10.6.24-1_on_cbl_mariner_2.0 | — | — |
| wolfssl | wolfssl | < 5.9.0 | 5.9.0 |
| wolfssl | wolfssl | >= 0 < 5.9.0-0.1 | 5.9.0-0.1 |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv4.07.2HIGHCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
osv7.2HIGH
vendor_debian7.2HIGH
vendor_msrc7.2HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2026-3548: Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsing CRL numbers: a heap-based buffer overflow could occur when improper
osv·2026-03-19·CVSS 7.2
CVE-2026-3548 [HIGH] CVE-2026-3548: Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsing CRL numbers: a heap-based buffer overflow could occur when improper
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.
GHSA
GHSA-86fv-q5vx-mw5m: Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsing CRL numbers: a heap-based buffer overflow could occur when improper
ghsa_unreviewed·2026-03-19
CVE-2026-3548 [HIGH] CWE-122 GHSA-86fv-q5vx-mw5m: Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsing CRL numbers: a heap-based buffer overflow could occur when improper
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.
Microsoft
Buffer overflow in CRL number parsing in wolfSSL
vendor_msrc·2026-03-10·CVSS 7.2
CVE-2026-3548 [HIGH] CWE-787 Buffer overflow in CRL number parsing in wolfSSL
Buffer overflow in CRL number parsing in wolfSSL
Mariner: Mariner
wolfSSL: wolfSSL
Customer Action Required: Yes
Debian
CVE-2026-3548: wolfssl - Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsi...
vendor_debian·2026·CVSS 7.2
CVE-2026-3548 [HIGH] CVE-2026-3548: wolfssl - Two buffer overflow vulnerabilities existed in the wolfSSL CRL parser when parsi...
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.
Scope: local
bookworm: open
bullseye: open
forky: resolved (fixed in 5.9.0-0.1)
sid: resolved (fixed in 5.9.0-0.1)
trixie: open
No detection rules found.
No public exploits indexed.
2026-03-19
Published