Dependency-Track End of Life (EOL) Dates & Support Timeline
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.
⚡Dependency-Track 4.14 reaches end of life on December 9, 2026. Plan your migration now — 169 days remaining.
📅 Get reminded before Dependency-Track 4.14 reaches EOL on December 9, 2026 — alerts 90, 30 & 7 days out.
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
Version
Latest Release
Release Date
EOL Date
Days
Status
4.7
4.7.1
Dec 16, 2022
Apr 18, 2023
1162 days past EOL
EOL
4.8
4.8.2
Apr 18, 2023
Oct 16, 2023
981 days past EOL
EOL
4.9
4.9.1
Oct 16, 2023
Dec 8, 2023
928 days past EOL
EOL
4.10
4.10.1
Dec 8, 2023
May 7, 2024
777 days past EOL
EOL
4.11
4.11.7
May 7, 2024
Oct 1, 2024
630 days past EOL
EOL
4.12
4.12.7
Oct 1, 2024
Apr 7, 2025
442 days past EOL
EOL
4.13
4.13.6
Apr 7, 2025
Mar 9, 2026
106 days past EOL
EOL
4.14
4.14.2
Mar 9, 2026
Dec 9, 2026
169 days remaining
Warning
5.0
5.0.2
Jun 9, 2026
TBD
Supported
Active
What does Dependency-Track end of life mean for your organization?
When a version of Dependency-Track 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Dependency-Track versions. This is a bridge, not a permanent solution — plan your migration in parallel.
endoflife.ai
Need Extended Support?
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
What is the end-of-life date for Dependency-Track?
The next Dependency-Track version reaching EOL is 4.14 on December 9, 2026. See the full table above for all version EOL dates.
When is the Dependency-Track support end date?
The next Dependency-Track support end date is December 9, 2026, when version 4.14 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Dependency-Track?
The latest active version of Dependency-Track is 5.0.2. Always verify against the table above as support windows can change.
What happens when Dependency-Track reaches end of life?
When Dependency-Track reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Dependency-Track?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Dependency-Track versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.