Squid · Lifecycle Status

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.

Squid 7.5 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
7.5
7 series
Next EOL
None upcoming
Active Versions
1
of 14 total
EOL Versions
13
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262.42.52.63.02.73.13.23.33.43.54567TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2.4 2.4.7 Mar 20, 2001 Jul 2, 2002 8712 days past EOL EOL
2.5 2.5.14 Sep 24, 2002 May 20, 2006 7294 days past EOL EOL
2.6 2.6.24 Jul 1, 2006 Mar 26, 2010 5888 days past EOL EOL
3.0 3.0.26 Dec 14, 2007 Aug 27, 2011 5369 days past EOL EOL
2.7 2.7.9 May 27, 2008 Mar 14, 2010 5900 days past EOL EOL
3.1 3.1.23 Mar 29, 2010 Jan 8, 2013 4869 days past EOL EOL
3.2 3.2.14 Aug 14, 2012 May 1, 2015 4026 days past EOL EOL
3.3 3.3.14 Feb 9, 2013 May 1, 2015 4026 days past EOL EOL
3.4 3.4.14 Dec 8, 2013 Aug 1, 2015 3934 days past EOL EOL
3.5 3.5.28 Jan 13, 2015 Aug 7, 2018 2832 days past EOL EOL
4 4.17 Jul 3, 2018 Oct 4, 2021 1678 days past EOL EOL
5 5.9 Jul 31, 2021 Jul 6, 2023 1038 days past EOL EOL
6 6.14 Jul 6, 2023 Jul 10, 2025 303 days past EOL EOL
7 7.5 Jul 10, 2025 Already EOL Supported Active

What does Squid end of life mean for your organization?

When a Squid 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 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Squid?
See the full table above for all Squid version EOL dates.
What is the latest supported version of Squid?
The latest active version of Squid is 7.5. Always verify against the table above as support windows can change.
What happens when Squid reaches end of life?
When Squid reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Squid?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Squid versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →