wolfSSL vulnerabilities and fixes
CVEs that mention wolfSSL, ranked by priority. 2 tracked.
wolfSSL has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2026-10-20. Highest priority: CVE-2026-55967 (score 33/100).
- CVE-2026-55967 HIGH 7.5 UPGRADE AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 GiB) were not properly
- CVE-2026-87866 HIGH n/a When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer do
FAQ
How do I fix wolfSSL vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is wolfSSL being exploited right now?
None of the tracked wolfSSL CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which wolfSSL CVE should I patch first?
CVE-2026-55967 currently ranks highest (33/100): AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 GiB) were not properly.
Newest wolfSSL CVEs
- CVE-2026-87866 HIGH n/a 2026-10-20: When built with wolfSSL, curl can successfully validate a pinned public key hash against a
- CVE-2026-55967 HIGH 7.5 2026-06-25: AES-GCM encryption/decryption with extremely large cumulative single message sizes (>64 Gi
Live from the NVD (last 120 days)
Loading…