Vulnerability Database · OSS-Fuzz · Package report

wireshark: vulnerability history, versions and safety

wireshark is a package in the OSS-Fuzz ecosystem. Vulert records 38 vulnerabilities for it across 120 releases, from Jun 2020 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
38 vulnerabilities recorded H9 M19 U10
i
1 with no fix published

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

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

Nothing new recorded in the last year.

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: one of the 38 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 38 vulnerabilities on record across 4 years, none in the last year.

What to do: Plan around the 1 vulnerability 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 38 over 4 years · 0 in the last year i
  • Latest disclosure 16 May 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 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
v4.6.7rc0 M1 No Details →
v4.5.0rc0 M1 No Details →
v4.4.9rc0 M2 No Details →
v4.4.8 M2 No Details →
wireshark-4.4.8 M2 No Details →
v4.4.8rc0 M2 No Details →
v4.4.7 M2 No Details →
wireshark-4.4.7 M2 No Details →
v4.4.7rc0 M1 No Details →
v4.4.6 M1 No Details →
wireshark-4.4.6 M1 No Details →
v4.4.6rc0 M1 No Details →
v4.4.5 M1 No Details →
wireshark-4.4.5 M1 No Details →
v4.4.5rc0 M1 No Details →
v4.4.4 M1 No Details →
wireshark-4.4.4 M1 No Details →
v4.4.4rc0 M1 No Details →
v4.4.3 M1 No Details →
wireshark-4.4.3 M1 No Details →
v4.4.3rc0 M1 No Details →
v4.4.2 M1 No Details →
wireshark-4.4.2 M1 No Details →
v4.4.2rc0 M1 No Details →
v4.4.1 M1 No Details →
wireshark-4.4.1 M1 No Details →
v4.4.1rc0 M1 No Details →
v4.4.0 M1 No Details →
wireshark-4.4.0 M1 No Details →
v4.4.0rc1 M1 No Details →
v4.4.0rc0 M1 No Details →
v4.3.2rc0 M1 No Details →
v4.3.1 M1 No Details →
v4.3.1rc0 M1 No Details →
v4.3.0 M1 No Details →
v4.3.0rc1 M1 No Details →
v4.3.0rc0 M1 No Details →
v4.2.13rc0 M1 No Details →
v4.2.12 M1 No Details →
wireshark-4.2.12 M1 No Details →
v4.2.12rc0 M1 No Details →
v4.2.11 M1 No Details →
wireshark-4.2.11 M1 No Details →
v4.2.11rc0 M1 No Details →
v4.2.10 M1 No Details →
wireshark-4.2.10 M1 No Details →
v4.2.10rc0 M1 No Details →
v4.2.9 M1 No Details →
wireshark-4.2.9 M1 No Details →
v4.2.9rc0 M1 No Details →
v4.2.8 M1 No Details →
wireshark-4.2.8 M1 No Details →
v4.2.8rc0 M1 No Details →
v4.2.7 M1 No Details →
wireshark-4.2.7 M1 No Details →
v4.2.7rc0 M1 No Details →
v4.2.6 M1 No Details →
wireshark-4.2.6 M1 No Details →
v4.2.6rc0 M1 No Details →
v4.2.5 M1 No Details →
wireshark-4.2.5 M1 No Details →
v4.2.5rc0 M1 No Details →
v4.2.4 M1 No Details →
wireshark-4.2.4 M1 No Details →
v4.2.4rc0 M1 No Details →
v4.2.3 M1 No Details →
wireshark-4.2.3 M1 No Details →
v4.2.3rc0 M1 No Details →
v4.2.2 M1 No Details →
wireshark-4.2.2 M1 No Details →
v4.2.2rc0 M1 No Details →
v4.2.1 M1 No Details →
wireshark-4.2.1 M1 No Details →
v4.2.1rc0 M1 No Details →
v4.2.0 M1 No Details →
wireshark-4.2.0 M1 No Details →
v4.2.0rc3 M1 No Details →
v4.2.0rc2 M1 No Details →
wireshark-4.2.0rc2 M1 No Details →
v4.2.0rc1 M1 No Details →
v4.2.0rc0 M1 No Details →
v4.1.1rc0 M1 No Details →
v4.1.0 M1 No Details →
v4.1.0rc0 M1 Yes Details →
v4.0.0rc1 M1 Yes Details →
v4.0.0rc0 M1 Yes Details →
v3.7.3rc0 M1 Yes Details →
v3.7.2 M1 Yes Details →
v3.5.0rc0 H1 M1 Yes Details →
v3.4.17rc0 H1 M1 Yes Details →
v3.4.16 H1 M1 Yes Details →
wireshark-3.4.16 H1 M1 Yes Details →
v3.4.16rc0 H1 M1 Yes Details →
v3.4.15 H1 M1 Yes Details →
wireshark-3.4.15 H1 M1 Yes Details →
v3.4.15rc0 H1 M1 Yes Details →
v3.4.14 H1 M1 Yes Details →
wireshark-3.4.14 H1 M1 Yes Details →
v3.4.14rc0 H1 M1 Yes Details →
v3.4.13 H1 M1 Yes Details →
wireshark-3.4.13 H1 M1 Yes Details →
v3.4.13rc0 H1 M1 Yes Details →
v3.4.12 H1 M1 Yes Details →
wireshark-3.4.12 H1 M1 Yes Details →
v3.4.12rc0 H1 M1 Yes Details →
v3.4.11 H1 M1 Yes Details →
wireshark-3.4.11 H1 M1 Yes Details →
v3.4.11rc0 H1 M1 Yes Details →
v3.4.10 H1 M1 Yes Details →
wireshark-3.4.10 H1 M1 Yes Details →
v3.4.10rc0 H1 M1 Yes Details →
v3.4.9 H1 M1 Yes Details →
wireshark-3.4.9 H1 M1 Yes Details →
v3.4.9rc0 H1 M1 Yes Details →
v3.4.8 H1 M1 Yes Details →
wireshark-3.4.8 H1 M1 Yes Details →
v3.4.8rc0 H1 M1 Yes Details →
v3.4.7 H1 M1 Yes Details →
wireshark-3.4.7 H1 M1 Yes Details →
v3.4.7rc0 H1 M1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 12
  • 2021 9
  • 2022 7
  • 2023 8
  • 2024 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 38 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for wireshark

The 5 most severe of 38 vulnerabilities recorded for this package

Search all 38 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Index-out-of-bounds Vulnerability in Wireshark Package N/A medium 76c83894a641ba15e513564bed6c42fb2e59dc02 16 May 2025
Global-buffer-overflow in dissect_wassp_sub_tlv in wireshark N/A unrated 71b59b18e4bb61d0e6da8bb2b26c87750570ae40 27 Jun 2020
Vulnerability in wireshark: UNKNOWN READ in dissect_oran_c_section N/A medium 53914b044780c3ebac42f465d7f54df27933d22e 07 Mar 2023
Heap-buffer-overflow in bytestring_to_str in wireshark N/A medium f17f1277607e5d745d889489f8da43b2a4e996a6 01 Jul 2020
Stack-buffer-overflow in tvb_memcpy in wireshark N/A high ba54b896969930491645aa3ec4125b76480add9c 01 Jul 2020

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 38 vulnerabilities for wireshark in OSS-Fuzz: 0 critical, 9 high, 19 medium and 0 low, plus 10 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does wireshark have?

38 vulnerabilities are recorded for wireshark in the OSS-Fuzz ecosystem: 0 critical, 9 high, 19 medium and 0 low, plus 10 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?

0 vulnerabilities were recorded for wireshark in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. 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.