EOL.Wiki EOL.Wiki
← ← Back to all products

Squid

Active
Server Software Latest Version: 7.4 Latest Release: Jan 20, 2026

Squid is a caching and forwarding HTTP web proxy supporting HTTP, HTTPS, FTP, and more.

Versions

14

Latest Version

7.4

Active Support

1

EOL

13

Lifecycle Timeline

Today
7
7
6
6
5
5
4
4
3.5
3.5
3.4
3.4
3.3
3.3
3.2
3.2
3.1
3.1
2.7
2.7
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
7Jul 10, 2025-No7.4No
Active
6Jul 6, 2023-Jul 10, 20256.14No
EOL
5Jul 31, 2021-Jul 6, 20235.9No
EOL
4Jul 3, 2018-Oct 4, 20214.17No
EOL
3.5Jan 13, 2015-Aug 7, 20183.5.28No
EOL
3.4Dec 8, 2013-Aug 1, 20153.4.14No
EOL
3.3Feb 9, 2013-May 1, 20153.3.14No
EOL
3.2Aug 14, 2012-May 1, 20153.2.14No
EOL
3.1Mar 29, 2010-Jan 8, 20133.1.23No
EOL
2.7May 27, 2008-Mar 14, 20102.7.9No
EOL
3.0Dec 14, 2007-Aug 27, 20113.0.26No
EOL
2.6Jul 1, 2006-Mar 26, 20102.6.24No
EOL
2.5Sep 24, 2002-May 20, 20062.5.14No
EOL
2.4Mar 20, 2001-Jul 2, 20022.4.7No
EOL

Frequently Asked Questions

Which versions of Squid have reached end of life?
The following Squid versions have reached end of life and no longer receive security updates: 6, 5, 4, 3.5, 3.4, 3.3, 3.2, 3.1 (and 5 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Squid 6?
Squid 6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Squid?
The latest version of Squid is 7.4, released in the 7 release cycle.
How many versions of Squid are currently supported?
Squid currently has 1 actively supported version(s): 7.
When does Squid 7 reach end of life?
Squid 7 does not have a specific end-of-life date announced yet.
What should I do when Squid reaches end of life?
When a Squid version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.