Complete end-of-life dates, support windows, and security status for all Apache Maven versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.1 | Jul 13, 2004 | Feb 18, 2014 | 4463 days past EOL | EOL |
| 2 | 2.2.1 | May 7, 2006 | Feb 18, 2014 | 4463 days past EOL | EOL |
| 3.0 | 3.0.5 | Oct 4, 2010 | Jun 28, 2013 | 4698 days past EOL | EOL |
| 3.1 | 3.1.1 | Jun 28, 2013 | Feb 14, 2014 | 4467 days past EOL | EOL |
| 3.2 | 3.2.5 | Feb 14, 2014 | Mar 13, 2015 | 4075 days past EOL | EOL |
| 3.3 | 3.3.9 | Mar 13, 2015 | Apr 3, 2017 | 3323 days past EOL | EOL |
| 3.5 | 3.5.4 | Apr 3, 2017 | Oct 24, 2018 | 2754 days past EOL | EOL |
| 3.6 | 3.6.3 | Oct 24, 2018 | Mar 30, 2021 | 1866 days past EOL | EOL |
| 3.8 | 3.8.9 | Mar 30, 2021 | Jun 14, 2025 | 329 days past EOL | EOL |
| 3.9 | 3.9.15 | Jan 31, 2023 | Already EOL | Supported | Active |
When a Apache Maven 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 Maven 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 →