Artifactory End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Artifactory versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.24 | 7.24.7 | Aug 11, 2021 | Feb 11, 2023 | 1275 days past EOL | EOL |
| 7.25 | 7.25.7 | Sep 2, 2021 | Mar 2, 2023 | 1256 days past EOL | EOL |
| 7.27 | 7.27.10 | Sep 30, 2021 | Mar 30, 2023 | 1228 days past EOL | EOL |
| 7.29 | 7.29.9 | Dec 5, 2021 | Jun 5, 2023 | 1161 days past EOL | EOL |
| 7.31 | 7.31.12 | Jan 10, 2022 | Jul 10, 2023 | 1126 days past EOL | EOL |
| 7.33 | 7.33.9 | Feb 3, 2022 | Aug 3, 2023 | 1102 days past EOL | EOL |
| 7.35 | 7.35.2 | Mar 1, 2022 | Sep 1, 2023 | 1073 days past EOL | EOL |
| 7.37 | 7.37.17 | Apr 14, 2022 | Oct 14, 2023 | 1030 days past EOL | EOL |
| 7.38 | 7.38.17 | May 8, 2022 | Nov 8, 2023 | 1005 days past EOL | EOL |
| 7.39 | 7.39.10 | Jun 20, 2022 | Dec 20, 2023 | 963 days past EOL | EOL |
| 7.41 | 7.41.14 | Jul 11, 2022 | Jan 11, 2024 | 941 days past EOL | EOL |
| 7.46 | 7.46.23 | Oct 11, 2022 | Apr 11, 2024 | 850 days past EOL | EOL |
| 7.47 | 7.47.16 | Dec 1, 2022 | Jun 1, 2024 | 799 days past EOL | EOL |
| 7.49 | 7.49.10 | Dec 29, 2022 | Jun 29, 2024 | 771 days past EOL | EOL |
| 7.55 | 7.55.17 | Feb 28, 2023 | Aug 28, 2024 | 711 days past EOL | EOL |
| 7.59 | 7.59.22 | May 28, 2023 | Nov 28, 2024 | 619 days past EOL | EOL |
| 7.63 | 7.63.22 | Jul 12, 2023 | Jan 12, 2025 | 574 days past EOL | EOL |
| 7.68 | 7.68.23 | Sep 11, 2023 | Mar 11, 2025 | 516 days past EOL | EOL |
| 7.71 | 7.71.25 | Oct 24, 2023 | Mar 24, 2025 | 503 days past EOL | EOL |
| 7.77 | 7.77.17 | Jan 24, 2024 | Jul 24, 2025 | 381 days past EOL | EOL |
| 7.84 | 7.84.23 | May 12, 2024 | Nov 12, 2025 | 270 days past EOL | EOL |
| 7.90 | 7.90.19 | Jul 25, 2024 | Jan 25, 2026 | 196 days past EOL | EOL |
| 7.98 | 7.98.19 | Oct 29, 2024 | Apr 29, 2026 | 102 days past EOL | EOL |
| 7.104 | 7.104.16 | Jan 29, 2025 | Jul 30, 2026 | 10 days past EOL | EOL |
| 7.111 | 7.111.14 | Apr 23, 2025 | Oct 23, 2026 | 75 days remaining | Warning |
| 7.117 | 7.117.21 | Jul 14, 2025 | Jan 14, 2027 | 158 days remaining | Warning |
| 7.125 | 7.125.14 | Oct 30, 2025 | Apr 30, 2027 | 264 days remaining | Active |
| 7.133 | 7.133.21 | Oct 30, 2025 | Apr 30, 2027 | 264 days remaining | Active |
| 7.146 | 7.146.12 | Apr 16, 2026 | Oct 16, 2027 | 433 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/artifactory)
What does Artifactory end of life mean for your organization?
When a version of Artifactory 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 Artifactory 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.
Your options when Artifactory reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Artifactory versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Artifactory has 24 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Artifactory exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.