Question 1

What happens when Dependency Track reaches end of life?

Accepted Answer

When Dependency Track reaches end of life, it stops receiving security patches, bug fixes, and new features. Currently, 7 Dependency Track versions are already EOL. The latest supported version is Dependency Track 4.14. Running an EOL version exposes your systems to unpatched security vulnerabilities with no official fix available.

Question 2

Is Dependency Track 4.14 still supported?

Accepted Answer

Yes. Dependency Track 4.14 is actively supported. It receives security patches and bug fixes. Check the version table above for the full list of supported Dependency Track releases and their exact end-of-life dates.

Question 3

Is it safe to use Dependency Track after end of life?

Accepted Answer

No. Running Dependency Track after EOL is not safe for production systems. Once a version reaches end of life, newly discovered CVEs are published publicly but never patched — leaving your systems permanently exposed. The only safe path is upgrading to an actively supported Dependency Track release.

Question 4

How to upgrade from Dependency Track 4.13 to Dependency Track 4.x?

Accepted Answer

To upgrade Dependency Track from 4.13 to 4.14: (1) review the official migration guide for breaking changes, (2) test your application against the new version in a staging environment, (3) update dependencies that have version constraints, (4) run your full test suite, (5) deploy with a rollback plan. The earlier you start, the more time you have to resolve compatibility issues before EOL.

Question 5

When is the next Dependency Track LTS version?

Accepted Answer

Not all Dependency Track releases have a designated LTS status. Check the version table above — LTS releases are marked with an "LTS" badge. Refer to the official Dependency Track release policy for information on upcoming long-term support versions.

Question 6

How long does Dependency Track support each version?

Accepted Answer

On average, Dependency Track supports each release for approximately 6 months (~0.5 years).  The exact EOL date for each version is listed in the table above.

Version	Released	Active support	EOL date	Until EOL	Latest	CVEs	Status
4.14	Mar 9, 2026	—	No	—	4.14.2	—	Active
4.13	Apr 7, 2025	—	Mar 9, 2026	92d ago	4.13.6	—	EOL
4.12	Oct 1, 2024	—	Apr 7, 2025	428d ago	4.12.7	—	EOL
4.11	May 7, 2024	—	Oct 1, 2024	616d ago	4.11.7	—	EOL
4.10	Dec 8, 2023	—	May 7, 2024	763d ago	4.10.1	—	EOL
4.9	Oct 16, 2023	—	Dec 8, 2023	914d ago	4.9.1	—	EOL
4.8	Apr 18, 2023	—	Oct 16, 2023	967d ago	4.8.2	—	EOL
4.7	Dec 16, 2022	—	Apr 18, 2023	1148d ago	4.7.1	—	EOL

Dependency Track End of Life Dates

Related technologies

Same category

Frequently Asked Questions