Wireshark End of Life (EOL) Dates & Support Timeline
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 | 5472 days past EOL | EOL |
| 1.2 | 1.2.18 | Jun 15, 2009 | Jun 30, 2011 | 5472 days past EOL | EOL |
| 1.4 | 1.4.15 | Aug 29, 2010 | Aug 30, 2012 | 5045 days past EOL | EOL |
| 1.6 | 1.6.16 | Jun 7, 2011 | Jun 7, 2013 | 4764 days past EOL | EOL |
| 1.8 | 1.8.15 | Jun 21, 2012 | Jun 21, 2014 | 4385 days past EOL | EOL |
| 1.10 | 1.10.14 | Jun 5, 2013 | Jun 5, 2015 | 4036 days past EOL | EOL |
| 1.12 | 1.12.13 | Jul 31, 2014 | Jul 31, 2016 | 3614 days past EOL | EOL |
| 2.0 | 2.0.16 | Nov 18, 2015 | Nov 18, 2017 | 3139 days past EOL | EOL |
| 2.2 | 2.2.17 | Sep 7, 2016 | Sep 7, 2018 | 2846 days past EOL | EOL |
| 2.4 | 2.4.16 | Jul 19, 2017 | Jul 19, 2019 | 2531 days past EOL | EOL |
| 2.6 LTS | 2.6.20 | Apr 18, 2018 | Oct 18, 2020 | 2074 days past EOL | EOL |
| 3.0 | 3.0.14 | Feb 28, 2019 | Oct 29, 2020 | 2063 days past EOL | EOL |
| 3.2 | 3.2.18 | Dec 18, 2019 | Nov 22, 2021 | 1674 days past EOL | EOL |
| 3.4 | 3.4.16 | Oct 29, 2020 | Sep 7, 2022 | 1385 days past EOL | EOL |
| 3.6 LTS | 3.6.24 | Nov 22, 2021 | May 22, 2024 | 762 days past EOL | EOL |
| 4.0 | 4.0.17 | Oct 4, 2022 | Aug 28, 2024 | 664 days past EOL | EOL |
| 4.2 | 4.2.14 | Nov 15, 2023 | Oct 8, 2025 | 258 days past EOL | EOL |
| 4.4 | 4.4.15 | Aug 28, 2024 | TBD | Supported | Active |
| 4.6 | 4.6.5 | Oct 8, 2025 | TBD | Supported | Active |
What does Wireshark end of life mean for your organization?
When a version of Wireshark 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Wireshark versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →