Squid End of Life Dates
other
Developers rely on tools that provide them with accurate and timely information to manage their projects effectively. Squid is one such tool, created to track end-of-life dates, supported versions, and security patch timelines for various software applications. Maintained by a team of experts, Squid has been a valuable resource for developers since its inception, helping them plan upgrades and migrations with ease. By providing critical information on software lifecycle management, Squid enables developers to focus on their core work, knowing that their dependencies are up to date and secure.
The end-of-life landscape for Squid itself is a testament to the dynamic nature of software development. With a total of 14 versions released so far, 13 of them have already reached their end-of-life, leaving only one active version. The latest stable version, 7.6, is the current benchmark for users. Although there is no next end-of-life date announced, the last one occurred on 2025-07-10, when version 6 reached its end of support. This information is crucial for developers who rely on Squid to plan their future upgrades and ensure continuity in their projects.
From a security perspective, Squid has an impeccable record, with no known vulnerabilities reported to date. The total number of CVEs tracked is 0, and consequently, there are no critical CVEs either. As a result, there is no most affected version, and no Known Exploited Vulnerability status applies. Given this clean slate, developers can continue to use Squid without worrying about potential security risks. However, it is essential for them to stay vigilant and keep their Squid versions up to date to ensure they can take advantage of any future security patches or updates that may be released.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 7 | Jul 10, 2025 | — | No | — | 7.6 | — | Active | |
| 6 | Jul 6, 2023 | — | Jul 10, 2025 | 379d ago | 6.14 | — | EOL | |
| 5 | Jul 31, 2021 | — | Jul 6, 2023 | 1114d ago | 5.9 | — | EOL | |
| 4 | Jul 3, 2018 | — | Oct 4, 2021 | 1754d ago | 4.17 | — | EOL | |
| 3.5 | Jan 13, 2015 | — | Aug 7, 2018 | 2908d ago | 3.5.28 | — | EOL | |
| 3.4 | Dec 8, 2013 | — | Aug 1, 2015 | 4010d ago | 3.4.14 | — | EOL | |
| 3.3 | Feb 9, 2013 | — | May 1, 2015 | 4102d ago | 3.3.14 | — | EOL | |
| 3.2 | Aug 14, 2012 | — | May 1, 2015 | 4102d ago | 3.2.14 | — | EOL | |
| 3.1 | Mar 29, 2010 | — | Jan 8, 2013 | 4945d ago | 3.1.23 | — | EOL | |
| 2.7 | May 27, 2008 | — | Mar 14, 2010 | 5976d ago | 2.7.9 | — | EOL | |
| 3.0 | Dec 14, 2007 | — | Aug 27, 2011 | 5445d ago | 3.0.26 | — | EOL | |
| 2.6 | Jul 1, 2006 | — | Mar 26, 2010 | 5964d ago | 2.6.24 | — | EOL | |
| 2.5 | Sep 24, 2002 | — | May 20, 2006 | 7370d ago | 2.5.14 | — | EOL | |
| 2.4 | Mar 20, 2001 | — | Jul 2, 2002 | 8788d ago | 2.4.7 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
