Complete end-of-life dates, support windows, and security status for all Wireshark versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0.16 | Mar 29, 2008 | Jun 30, 2011 | 5427 days past EOL | EOL |
| 1.2 | 1.2.18 | Jun 15, 2009 | Jun 30, 2011 | 5427 days past EOL | EOL |
| 1.4 | 1.4.15 | Aug 29, 2010 | Aug 30, 2012 | 5000 days past EOL | EOL |
| 1.6 | 1.6.16 | Jun 7, 2011 | Jun 7, 2013 | 4719 days past EOL | EOL |
| 1.8 | 1.8.15 | Jun 21, 2012 | Jun 21, 2014 | 4340 days past EOL | EOL |
| 1.10 | 1.10.14 | Jun 5, 2013 | Jun 5, 2015 | 3991 days past EOL | EOL |
| 1.12 | 1.12.13 | Jul 31, 2014 | Jul 31, 2016 | 3569 days past EOL | EOL |
| 2.0 | 2.0.16 | Nov 18, 2015 | Nov 18, 2017 | 3094 days past EOL | EOL |
| 2.2 | 2.2.17 | Sep 7, 2016 | Sep 7, 2018 | 2801 days past EOL | EOL |
| 2.4 | 2.4.16 | Jul 19, 2017 | Jul 19, 2019 | 2486 days past EOL | EOL |
| 2.6 LTS | 2.6.20 | Apr 18, 2018 | Oct 18, 2020 | 2029 days past EOL | EOL |
| 3.0 | 3.0.14 | Feb 28, 2019 | Oct 29, 2020 | 2018 days past EOL | EOL |
| 3.2 | 3.2.18 | Dec 18, 2019 | Nov 22, 2021 | 1629 days past EOL | EOL |
| 3.4 | 3.4.16 | Oct 29, 2020 | Sep 7, 2022 | 1340 days past EOL | EOL |
| 3.6 LTS | 3.6.24 | Nov 22, 2021 | May 22, 2024 | 717 days past EOL | EOL |
| 4.0 | 4.0.17 | Oct 4, 2022 | Aug 28, 2024 | 619 days past EOL | EOL |
| 4.2 | 4.2.14 | Nov 15, 2023 | Oct 8, 2025 | 213 days past EOL | EOL |
| 4.4 | 4.4.15 | Aug 28, 2024 | Already EOL | Supported | Active |
| 4.6 | 4.6.5 | Oct 8, 2025 | Already EOL | Supported | Active |
When a Wireshark version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Wireshark should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →