Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
| Date | Total | Labels |
|---|
| 2026-03-19 | 2 | Disclosure2 |
| 2026-03-23 | 1 | Disclosure1 |
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 improperly storing the CRL… https://www.cve.org/CVERecord?id=CVE-2026-3548
Post summary
The passage announces two heap‑based buffer overflow vulnerabilities in the wolfSSL CRL parser.
CVE-2026-3548 Buffer Overflow Vulnerabilities in wolfSSL CRL Parser Enabling Arbitrary Write https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-3548
Post summary
The post announces CVE-2026-3548, a buffer overflow in wolfSSL’s CRL parser that leads to arbitrary write, with no PoC, exploit code, or patch details provided.
🚨 CYBERDUDEBIVASH SENTINEL APEX ALERT 🚨 Threat: CVE-2026-3548 - Buffer overflow in CRL number parsing in wolfSSL Intel Report: https://ift.tt/GI9nXiL
Post summary
An alert reports CVE-2026-3548 as a buffer overflow in wolfSSL's CRL number parsing, with an Intel report cited but no PoC, exploit, or patch details.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | wolfssl | wolfssl | - | - | - |