Squid End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Squid versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.4 | 2.4.7 | Mar 20, 2001 | Jul 2, 2002 | 8757 days past EOL | EOL |
| 2.5 | 2.5.14 | Sep 24, 2002 | May 20, 2006 | 7339 days past EOL | EOL |
| 2.6 | 2.6.24 | Jul 1, 2006 | Mar 26, 2010 | 5933 days past EOL | EOL |
| 3.0 | 3.0.26 | Dec 14, 2007 | Aug 27, 2011 | 5414 days past EOL | EOL |
| 2.7 | 2.7.9 | May 27, 2008 | Mar 14, 2010 | 5945 days past EOL | EOL |
| 3.1 | 3.1.23 | Mar 29, 2010 | Jan 8, 2013 | 4914 days past EOL | EOL |
| 3.2 | 3.2.14 | Aug 14, 2012 | May 1, 2015 | 4071 days past EOL | EOL |
| 3.3 | 3.3.14 | Feb 9, 2013 | May 1, 2015 | 4071 days past EOL | EOL |
| 3.4 | 3.4.14 | Dec 8, 2013 | Aug 1, 2015 | 3979 days past EOL | EOL |
| 3.5 | 3.5.28 | Jan 13, 2015 | Aug 7, 2018 | 2877 days past EOL | EOL |
| 4 | 4.17 | Jul 3, 2018 | Oct 4, 2021 | 1723 days past EOL | EOL |
| 5 | 5.9 | Jul 31, 2021 | Jul 6, 2023 | 1083 days past EOL | EOL |
| 6 | 6.14 | Jul 6, 2023 | Jul 10, 2025 | 348 days past EOL | EOL |
| 7 | 7.6 | Jul 10, 2025 | TBD | Supported | Active |
What does Squid end of life mean for your organization?
When a version of Squid 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 Squid 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 Squid 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 →