CISA list

Wireshark versions

Wireshark: update to 4.6.16 or 4.4.20. 4.2 and older no longer get fixes.

Data: .

Which Wireshark branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.

Which Wireshark branch to run
BranchStatusNewest safe releaseUpgrade to
4.6150 CVE records that this page readsBug and security fixes, no end date announced4.6.164.6.16 (this branch)
4.4137 CVE records that this page readsSecurity fixes only, no end date announced4.4.204.4.20 (this branch)
4.215 CVE records that this page readsEnded on 8 October 2025None, the branch has ended4.4.20 (move to 4.4)
4.035 CVE records that this page readsEnded on 28 August 2024None, the branch has ended4.4.20 (move to 4.4)
3.640 CVE records that this page readsEnded on 22 May 2024None, the branch has ended4.4.20 (move to 4.4)
3.419 CVE records that this page readsEnded on 7 September 2022None, the branch has ended4.4.20 (move to 4.4)
3.27 CVE records that this page readsEnded on 22 November 2021None, the branch has ended4.4.20 (move to 4.4)
3.0Ended on 29 October 2020None, the branch has ended4.4.20 (move to 4.4)
2.6Ended on 18 October 2020None, the branch has ended4.4.20 (move to 4.4)
2.4Ended on 19 July 2019None, the branch has ended4.4.20 (move to 4.4)
2.2Ended on 7 September 2018None, the branch has ended4.4.20 (move to 4.4)
2.0Ended on 18 November 2017None, the branch has ended4.4.20 (move to 4.4)
1.12Ended on 31 July 2016None, the branch has ended4.4.20 (move to 4.4)
1.10Ended on 5 June 2015None, the branch has ended4.4.20 (move to 4.4)
1.8Ended on 21 June 2014None, the branch has ended4.4.20 (move to 4.4)
1.6Ended on 7 June 2013None, the branch has ended4.4.20 (move to 4.4)
1.4Ended on 30 August 2012None, the branch has ended4.4.20 (move to 4.4)
1.2Ended on 30 June 2011None, the branch has ended4.4.20 (move to 4.4)
1.0Ended on 30 June 2011None, the branch has ended4.4.20 (move to 4.4)

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 222 CVE records that the CVE Numbering Authorities AHA and GitLab (as the CVE List names them) published and that name Wireshark. The fixes are from the 219 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

A branch that has ended is rarely named in a new record. That is not a sign that it is safe.

Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.

3 records are not placed on a branch, so no branch or release row counts them: CVE-2023-0666, CVE-2023-0667 and CVE-2023-0668.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)