Complete end-of-life dates, support windows, and security status for all Apache Subversion versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 LTS | 1.0.9 | Feb 23, 2004 | Supported indefinitely | Supported | Active |
| 1.1 LTS | 1.1.4 | Sep 29, 2004 | Supported indefinitely | Supported | Active |
| 1.2 LTS | 1.2.3 | May 21, 2005 | Supported indefinitely | Supported | Active |
| 1.3 LTS | 1.3.2 | Dec 30, 2005 | Supported indefinitely | Supported | Active |
| 1.4 LTS | 1.4.6 | Sep 10, 2006 | Supported indefinitely | Supported | Active |
| 1.5 LTS | 1.5.9 | Jun 19, 2008 | Supported indefinitely | Supported | Active |
| 1.6 LTS | 1.6.23 | Mar 20, 2009 | Supported indefinitely | Supported | Active |
| 1.7 LTS | 1.7.22 | Oct 11, 2011 | Supported indefinitely | Supported | Active |
| 1.8 LTS | 1.8.19 | Jun 18, 2013 | Supported indefinitely | Supported | Active |
| 1.9 LTS | 1.9.12 | Aug 5, 2015 | Supported indefinitely | Supported | Active |
| 1.10 LTS | 1.10.8 | Apr 12, 2018 | Supported indefinitely | Supported | Active |
| 1.11 | 1.11.1 | Oct 30, 2018 | Supported indefinitely | Supported | Active |
| 1.12 | 1.12.2 | Apr 24, 2019 | Supported indefinitely | Supported | Active |
| 1.13 | 1.13.0 | Oct 30, 2019 | Supported indefinitely | Supported | Active |
| 1.14 LTS | 1.14.5 | May 27, 2020 | Already EOL | Supported | Active |
When a Apache Subversion 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 Apache Subversion 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →