Wireshark vulnerabilities: known CVEs & security history
Wireshark · Network tools · 736 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Wireshark release lines — 736 in total. A CVE here doesn't mean your version is affected — check Wireshark's current status and the safe version to run.
Known Wireshark CVEs
Actively-exploited and most-severe first. Showing the top 80 of 736. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2018-6836 | critical | 9.8 | 3% | 2018 |
| CVE-2011-0444 | high | 10 | 7% | 2011 |
| CVE-2010-2995 | high | 10 | 7% | 2010 |
| CVE-2010-2994 | high | 10 | 2% | 2010 |
| CVE-2009-1266 | high | 10 | 2% | 2009 |
| CVE-2009-1210 | high | 10 | 15% | 2009 |
| CVE-2008-3146 | high | 10 | 4% | 2008 |
| CVE-2007-6112 | high | 10 | 6% | 2007 |
| CVE-2007-6114 | high | 10 | 6% | 2007 |
| CVE-2007-6115 | high | 10 | 6% | 2007 |
| CVE-2006-3628 | high | 10 | 6% | 2006 |
| CVE-2014-4174 | high | 9.3 | 6% | 2014 |
| CVE-2014-2299 | high | 9.3 | 47% | 2014 |
| CVE-2011-3360 | high | 9.3 | 36% | 2011 |
| CVE-2011-1591 | high | 9.3 | 42% | 2011 |
| CVE-2011-0024 | high | 9.3 | 5% | 2011 |
| CVE-2010-4538 | high | 9.3 | 29% | 2011 |
| CVE-2010-3133 | high | 9.3 | 9% | 2010 |
| CVE-2009-4376 | high | 9.3 | 7% | 2009 |
| CVE-2009-3829 | high | 9.3 | 6% | 2009 |
| CVE-2026-5402 | high | 8.8 | 0% | 2026 |
| CVE-2012-4297 | high | 8.3 | 2% | 2012 |
| CVE-2010-2287 | high | 8.3 | 1% | 2010 |
| CVE-2010-2284 | high | 8.3 | 1% | 2010 |
| CVE-2026-5405 | high | 7.8 | 0% | 2026 |
| CVE-2026-5403 | high | 7.8 | 0% | 2026 |
| CVE-2025-13499 | high | 7.8 | 0% | 2025 |
| CVE-2025-9817 | high | 7.8 | 0% | 2025 |
| CVE-2025-5601 | high | 7.8 | 0% | 2025 |
| CVE-2025-1492 | high | 7.8 | 0% | 2025 |
| CVE-2024-11596 | high | 7.8 | 0% | 2024 |
| CVE-2024-11595 | high | 7.8 | 0% | 2024 |
| CVE-2024-9781 | high | 7.8 | 0% | 2024 |
| CVE-2024-9780 | high | 7.8 | 0% | 2024 |
| CVE-2024-8250 | high | 7.8 | 0% | 2024 |
| CVE-2024-2955 | high | 7.8 | 1% | 2024 |
| CVE-2023-6175 | high | 7.8 | 3% | 2024 |
| CVE-2024-0211 | high | 7.8 | 1% | 2024 |
| CVE-2024-0210 | high | 7.8 | 0% | 2024 |
| CVE-2024-0209 | high | 7.8 | 1% | 2024 |
| CVE-2024-0208 | high | 7.8 | 2% | 2024 |
| CVE-2024-0207 | high | 7.8 | 0% | 2024 |
| CVE-2016-2521 | high | 7.8 | 0% | 2016 |
| CVE-2015-3812 | high | 7.8 | 4% | 2015 |
| CVE-2015-3810 | high | 7.8 | 3% | 2015 |
| CVE-2015-3809 | high | 7.8 | 3% | 2015 |
| CVE-2015-3808 | high | 7.8 | 3% | 2015 |
| CVE-2013-4929 | high | 7.8 | 4% | 2013 |
| CVE-2013-4928 | high | 7.8 | 3% | 2013 |
| CVE-2013-4927 | high | 7.8 | 4% | 2013 |
| CVE-2013-3561 | high | 7.8 | 2% | 2013 |
| CVE-2013-2487 | high | 7.8 | 3% | 2013 |
| CVE-2009-3241 | high | 7.8 | 10% | 2009 |
| CVE-2007-6118 | high | 7.8 | 2% | 2007 |
| CVE-2007-6119 | high | 7.8 | 3% | 2007 |
| CVE-2007-3391 | high | 7.8 | 2% | 2007 |
| CVE-2024-24479 | high | 7.5 | 1% | 2024 |
| CVE-2024-24476 | high | 7.5 | 1% | 2024 |
| CVE-2024-24478 | high | 7.5 | 1% | 2024 |
| CVE-2021-4190 | high | 7.5 | 3% | 2021 |
| CVE-2021-4185 | high | 7.5 | 4% | 2021 |
| CVE-2021-4184 | high | 7.5 | 4% | 2021 |
| CVE-2021-4182 | high | 7.5 | 3% | 2021 |
| CVE-2021-4181 | high | 7.5 | 4% | 2021 |
| CVE-2021-39929 | high | 7.5 | 4% | 2021 |
| CVE-2021-39926 | high | 7.5 | 8% | 2021 |
| CVE-2021-39925 | high | 7.5 | 8% | 2021 |
| CVE-2021-39924 | high | 7.5 | 5% | 2021 |
| CVE-2021-39923 | high | 7.5 | 2% | 2021 |
| CVE-2021-39922 | high | 7.5 | 5% | 2021 |
| CVE-2021-39921 | high | 7.5 | 3% | 2021 |
| CVE-2021-39928 | high | 7.5 | 6% | 2021 |
| CVE-2021-39920 | high | 7.5 | 3% | 2021 |
| CVE-2021-22235 | high | 7.5 | 3% | 2021 |
| CVE-2021-22222 | high | 7.5 | 2% | 2021 |
| CVE-2020-28030 | high | 7.5 | 2% | 2020 |
| CVE-2020-26575 | high | 7.5 | 3% | 2020 |
| CVE-2020-25866 | high | 7.5 | 4% | 2020 |
| CVE-2020-25863 | high | 7.5 | 5% | 2020 |
| CVE-2020-25862 | high | 7.5 | 2% | 2020 |
656 older / lower-severity CVEs not shown — see Wireshark's full record.
Is my Wireshark 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 Wireshark version → · Monitor Wireshark for new CVEs →
Wireshark vulnerabilities — frequently asked
How many known vulnerabilities does Wireshark have?
IsItPatched tracks 736 CVEs for Wireshark. 1 is critical-severity and 240 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Wireshark have any actively-exploited vulnerabilities?
None of Wireshark'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 Wireshark vulnerability?
Among tracked issues, CVE-2018-6836 (CRITICAL, CVSS 9.8) ranks highest — a CWE-763 weakness.
Is Wireshark safe to use?
It depends on the version. The latest supported Wireshark 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: Wireshark security status · Wireshark end-of-life · actively-exploited CVEs. Always verify against Wireshark's advisories — see our disclaimer.