Complete end-of-life dates, support windows, and security status for all Dependency Track versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 4.7 | 4.7.1 | Dec 16, 2022 | Apr 18, 2023 | 1117 days past EOL | EOL |
| 4.8 | 4.8.2 | Apr 18, 2023 | Oct 16, 2023 | 936 days past EOL | EOL |
| 4.9 | 4.9.1 | Oct 16, 2023 | Dec 8, 2023 | 883 days past EOL | EOL |
| 4.10 | 4.10.1 | Dec 8, 2023 | May 7, 2024 | 732 days past EOL | EOL |
| 4.11 | 4.11.7 | May 7, 2024 | Oct 1, 2024 | 585 days past EOL | EOL |
| 4.12 | 4.12.7 | Oct 1, 2024 | Apr 7, 2025 | 397 days past EOL | EOL |
| 4.13 | 4.13.6 | Apr 7, 2025 | Mar 9, 2026 | 61 days past EOL | EOL |
| 4.14 | 4.14.2 | Mar 9, 2026 | Already EOL | Supported | Active |
When a Dependency Track 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 Dependency Track 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 →