Wireshark 1.6 · Version Status
Wireshark 1.6 End of Life Date
Wireshark 1.6 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Wireshark 1.6 is past end of life. This version no longer receives security patches. 4719 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 7, 2013
4719 days past EOL
Latest Release
1.6.16
Standard release
Release Date
Jun 7, 2011
Wireshark 1.6 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.16 |
Jun 30, 2011 |
EOL |
| 1.2 |
1.2.18 |
Jun 30, 2011 |
EOL |
| 1.4 |
1.4.15 |
Aug 30, 2012 |
EOL |
| → 1.6 |
1.6.16 |
Jun 7, 2013 |
EOL |
| 1.8 |
1.8.15 |
Jun 21, 2014 |
EOL |
| 1.10 |
1.10.14 |
Jun 5, 2015 |
EOL |
| 1.12 |
1.12.13 |
Jul 31, 2016 |
EOL |
| 2.0 |
2.0.16 |
Nov 18, 2017 |
EOL |
What does Wireshark 1.6 end of life mean?
When Wireshark 1.6 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Wireshark 1.6 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Wireshark 4.6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Wireshark 1.6 reach end of life?
Wireshark 1.6 reached end of life on June 7, 2013. This version is no longer receiving security patches.
Is Wireshark 1.6 still supported?
No. Wireshark 1.6 reached end of life on June 7, 2013 and is no longer receiving security patches.
What should I upgrade to from Wireshark 1.6?
The recommended upgrade from Wireshark 1.6 is
Wireshark 4.6 — the latest actively supported version. Check the
Wireshark full timeline for all supported versions.
What are the security risks of running Wireshark 1.6 past EOL?
When Wireshark 1.6 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Wireshark should migrate immediately or implement compensating controls.