wolfSSL vulnerabilities: known CVEs & security history
wolfSSL · Security / Crypto · 141 tracked CVEs · 0 actively exploited · updated August 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all wolfSSL release lines — 141 in total. A CVE here doesn't mean your version is affected — check wolfSSL's current status and the safe version to run.
Known wolfSSL CVEs
Actively-exploited and most-severe first. Showing the top 80 of 141. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-7531 | critical | 9.8 | 0% | 2026 |
| CVE-2026-5264 | critical | 9.8 | 0% | 2026 |
| CVE-2026-5187 | critical | 9.8 | 0% | 2026 |
| CVE-2026-4395 | critical | 9.8 | 0% | 2026 |
| CVE-2026-3849 | critical | 9.8 | 0% | 2026 |
| CVE-2026-3549 | critical | 9.8 | 0% | 2026 |
| CVE-2026-3548 | critical | 9.8 | 0% | 2026 |
| CVE-2025-7394 | critical | 9.8 | 0% | 2025 |
| CVE-2021-37155 | critical | 9.8 | 1% | 2021 |
| CVE-2020-36177 | critical | 9.8 | 4% | 2021 |
| CVE-2014-2898 | critical | 9.8 | 3% | 2020 |
| CVE-2014-2897 | critical | 9.8 | 3% | 2020 |
| CVE-2014-2896 | critical | 9.8 | 3% | 2020 |
| CVE-2019-16748 | critical | 9.8 | 1% | 2019 |
| CVE-2019-15651 | critical | 9.8 | 1% | 2019 |
| CVE-2019-11873 | critical | 9.8 | 9% | 2019 |
| CVE-2019-6439 | critical | 9.8 | 3% | 2019 |
| CVE-2017-2800 | critical | 9.8 | 9% | 2017 |
| CVE-2026-6094 | critical | 9.1 | 0% | 2026 |
| CVE-2026-5393 | critical | 9.1 | 0% | 2026 |
| CVE-2026-5503 | critical | 9.1 | 0% | 2026 |
| CVE-2026-5194 | critical | 9.1 | 0% | 2026 |
| CVE-2023-3724 | critical | 9.1 | 1% | 2023 |
| CVE-2022-42905 | critical | 9.1 | 2% | 2022 |
| CVE-2022-23408 | critical | 9.1 | 1% | 2022 |
| CVE-2025-11931 | high | 8.2 | 0% | 2025 |
| CVE-2026-5501 | high | 8.1 | 0% | 2026 |
| CVE-2026-5479 | high | 8.1 | 0% | 2026 |
| CVE-2026-5466 | high | 8.1 | 0% | 2026 |
| CVE-2026-5188 | high | 8.1 | 0% | 2026 |
| CVE-2026-2646 | high | 8.1 | 0% | 2026 |
| CVE-2021-3336 | high | 8.1 | 1% | 2021 |
| CVE-2026-5295 | high | 8 | 0% | 2026 |
| CVE-2017-8854 | high | 7.8 | 2% | 2017 |
| CVE-2026-8720 | high | 7.5 | 0% | 2026 |
| CVE-2026-7532 | high | 7.5 | 0% | 2026 |
| CVE-2026-7511 | high | 7.5 | 0% | 2026 |
| CVE-2026-6331 | high | 7.5 | 0% | 2026 |
| CVE-2026-6325 | high | 7.5 | 0% | 2026 |
| CVE-2026-11703 | high | 7.5 | 0% | 2026 |
| CVE-2026-6731 | high | 7.5 | 0% | 2026 |
| CVE-2026-6679 | high | 7.5 | 0% | 2026 |
| CVE-2026-55960 | high | 7.5 | 0% | 2026 |
| CVE-2026-55958 | high | 7.5 | 0% | 2026 |
| CVE-2026-12340 | high | 7.5 | 0% | 2026 |
| CVE-2026-11310 | high | 7.5 | 0% | 2026 |
| CVE-2026-10512 | high | 7.5 | 0% | 2026 |
| CVE-2026-10097 | high | 7.5 | 0% | 2026 |
| CVE-2026-55967 | high | 7.5 | 0% | 2026 |
| CVE-2026-55961 | high | 7.5 | 0% | 2026 |
| CVE-2026-11999 | high | 7.5 | 0% | 2026 |
| CVE-2026-5477 | high | 7.5 | 0% | 2026 |
| CVE-2026-5447 | high | 7.5 | 0% | 2026 |
| CVE-2026-3547 | high | 7.5 | 0% | 2026 |
| CVE-2026-2645 | high | 7.5 | 0% | 2026 |
| CVE-2025-12888 | high | 7.5 | 0% | 2025 |
| CVE-2025-11935 | high | 7.5 | 0% | 2025 |
| CVE-2024-5991 | high | 7.5 | 1% | 2024 |
| CVE-2024-0901 | high | 7.5 | 1% | 2024 |
| CVE-2022-39173 | high | 7.5 | 4% | 2022 |
| CVE-2022-38152 | high | 7.5 | 2% | 2022 |
| CVE-2022-34293 | high | 7.5 | 1% | 2022 |
| CVE-2022-25640 | high | 7.5 | 1% | 2022 |
| CVE-2020-12457 | high | 7.5 | 2% | 2020 |
| CVE-2020-11713 | high | 7.5 | 2% | 2020 |
| CVE-2019-19962 | high | 7.5 | 1% | 2019 |
| CVE-2014-2904 | high | 7.5 | 1% | 2019 |
| CVE-2014-2902 | high | 7.5 | 1% | 2019 |
| CVE-2014-2901 | high | 7.5 | 1% | 2019 |
| CVE-2019-18840 | high | 7.5 | 2% | 2019 |
| CVE-2017-13099 | high | 7.5 | 25% | 2017 |
| CVE-2017-8855 | high | 7.5 | 1% | 2017 |
| CVE-2015-6925 | high | 7.5 | 3% | 2016 |
| CVE-2026-5446 | high | 7.1 | 0% | 2026 |
| CVE-2026-0819 | high | 7.1 | 0% | 2026 |
| CVE-2020-15309 | high | 7 | 0% | 2020 |
| CVE-2020-24613 | medium | 6.8 | 1% | 2020 |
| CVE-2024-2881 | medium | 6.7 | 0% | 2024 |
| CVE-2026-6330 | medium | 6.5 | 0% | 2026 |
| CVE-2026-6329 | medium | 6.5 | 0% | 2026 |
61 older / lower-severity CVEs not shown — see wolfSSL's full record.
Is my wolfSSL version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your wolfSSL version → · Monitor wolfSSL for new CVEs →
wolfSSL vulnerabilities — frequently asked
How many known vulnerabilities does wolfSSL have?
IsItPatched tracks 141 CVEs for wolfSSL. 25 are critical-severity and 51 high-severity. These span every release line — what matters is whether the version you run is affected.
Does wolfSSL have any actively-exploited vulnerabilities?
None of wolfSSL's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe wolfSSL vulnerability?
Among tracked issues, CVE-2026-7531 (CRITICAL, CVSS 9.8) ranks highest — a Use-after-free weakness.
Is wolfSSL safe to use?
It depends on the version. The latest supported wolfSSL release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: wolfSSL security status · wolfSSL end-of-life · actively-exploited CVEs. Always verify against wolfSSL's advisories — see our disclaimer.