Vulnerability Database · Debian · Package report

wireshark: vulnerability history, versions and safety

wireshark is a package in the Debian ecosystem. Vulert records 1,313 vulnerabilities for it across 69 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1,313 vulnerabilities recorded U1313
i
100 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
88 in the last 12 months

Most recent disclosure 19 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on wireshark i

Updated on 23 Oct 2026

Careful: 100 of the 1,313 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 1,313 vulnerabilities on record across 2026 years, 88 in the last year.

What to do: Plan around the 100 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 1,313 over 2026 years · 88 in the last year i
  • Latest disclosure 19 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 100 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for wireshark, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
4.6.6-2 U26 No Details →
4.6.6-1 U39 No Details →
4.6.5-1 U40 No Details →
4.6.4-1 U82 No Details →
4.6.3-1 U85 No Details →
4.6.2-3 U89 No Details →
4.6.2-1 U89 No Details →
4.6.1-2 U92 No Details →
4.6.1-1 U92 No Details →
4.6.0-1 U93 No Details →
4.6.0-0exp1 U94 No Details →
4.6.0~rc1-0exp2 U94 No Details →
4.6.0~rc1-0exp1 U94 No Details →
4.4.9-1 U95 No Details →
4.4.8-0exp1 U100 No Details →
4.4.7-1 U100 No Details →
4.4.7-0exp1 U100 No Details →
4.4.6-2 U100 No Details →
4.4.6-1 U100 No Details →
4.4.5-1 U100 No Details →
4.4.4-1 U100 No Details →
4.4.3-1 U100 No Details →
4.4.2-1 U100 No Details →
4.4.1-1 U100 No Details →
4.4.0-1 U100 No Details →
4.4.0-0exp2 U100 No Details →
4.4.0-0exp1 U100 No Details →
4.2.6-1 U100 No Details →
4.2.5-2 U100 No Details →
4.2.5-1 U100 No Details →
4.2.4-1 U100 No Details →
4.2.2-1.1 U100 No Details →
4.2.2-1.1~exp1 U100 No Details →
4.2.2-1 U100 No Details →
4.2.0-1 U100 No Details →
4.2.0-1~exp0 U100 No Details →
4.2.0~rc3-1~exp1 U100 No Details →
4.0.11-1 U100 No Details →
4.0.11-1~deb12u1 U100 No Details →
4.0.10-1 U100 No Details →
4.0.8-1 U100 No Details →
4.0.7-1 U100 No Details →
4.0.6-1 U100 No Details →
4.0.6-1~deb12u1 U100 No Details →
4.0.6-1~exp1 U100 No Details →
4.0.5-1~exp1 U100 No Details →
4.0.3-1 U100 No Details →
4.0.2-1 U100 No Details →
4.0.1-1 U100 No Details →
4.0.0-1 U100 No Details →
4.0.0-1~exp0 U100 No Details →
3.6.8-1 U100 No Details →
3.6.7-1 U100 No Details →
3.6.6-1 U100 No Details →
3.6.5-1 U100 No Details →
3.6.3-1 U100 No Details →
3.6.2-2 U100 No Details →
3.6.2-1 U100 No Details →
3.6.0-1 U100 No Details →
3.6.0~rc1-0exp1 U100 No Details →
3.4.16-0+deb11u2 U85 No Details →
3.4.16-0+deb11u1 U101 No Details →
3.4.10-0+deb11u1 U196 No Details →
3.4.9-1 U221 No Details →
3.4.8-1 U221 No Details →
3.4.7-1 U221 No Details →
3.4.7-1~exp1 U221 No Details →
3.4.6-1~exp1 U221 No Details →
3.4.4-1 U221 No Details →

Newest 69 of 69 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 6
  • 2006 30
  • 2007 50
  • 2008 44
  • 2009 42
  • 2010 26
  • 2011 58
  • 2012 92
  • 2013 160
  • 2014 58
  • 2015 66
  • 2016 178
  • 2017 74
  • 2018 134
  • 2019 36
  • 2020 38
  • 2021 43
  • 2022 12
  • 2023 52
  • 2024 23
  • 2025 4
  • 2026 87

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 88 of the 1,313 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About wireshark

Is wireshark safe to use?

Vulert records 1,313 vulnerabilities for wireshark in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 1313 not yet rated. 100 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does wireshark have?

1,313 vulnerabilities are recorded for wireshark in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1313 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wireshark vulnerabilities disclosed?

88 vulnerabilities were recorded for wireshark in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of wireshark are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor wireshark for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wireshark version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.