Every Confluence version dies two years after release —
and the 7.x holdouts are three LTS lines behind.
Atlassian’s support policy for Confluence Data Center is unusually exact: every version is supported for two years after its release, to the day. That single rule produces the entire lifecycle table below — and it retires a Confluence version every month or two, whether anyone noticed or not.
The reason this page exists is what people search for. “Confluence 7.13” is still a query with steady demand in 2026 — and Confluence 7.13 LTS reached end of life on August 17, 2023, three years ago today. Its successors 7.19 and 8.5 have died since. Someone searching for 7.13 today is not doing an academic lookup; they are running it, on the product with more entries in CISA’s Known Exploited Vulnerabilities catalog than anything else we track this week.
The two-year clock
Atlassian’s end-of-life policy states it plainly: the company “supports releases for two years after the initial feature or Long-Term Support (LTS) release.” No tiers, no paid extension, no exceptions for LTS beyond the label. An LTS release gets the same two years as a feature release; the difference is that LTS lines receive bug-fix and security backports for their whole window, while feature releases are superseded quickly.
Two consequences fall out. First, the retirement cadence is relentless — a version dies about every eight weeks in the current line. Second, the LTS date is the only date worth planning around: it is the version that keeps receiving fixes for its full two years. That makes the LTS end dates the spine of the table:
Every version’s date
| Version | Type | Released | End of life | Status | Risk score |
|---|---|---|---|---|---|
| 10.2 | LTS | 2025-12-02 | 2027-12-02 | Supported | 30 |
| 9.2 | LTS | 2024-12-09 | 2026-12-10 | Supported (4 months left) | 38 |
| 8.5 | LTS | 2023-08-21 | 2025-12-15 | End of life | 60 |
| 7.19 | LTS | 2022-07-27 | 2024-12-13 | End of life | 65 |
| 7.13 | LTS | 2021-08-15 | 2023-08-17 | End of life | 70 |
The LTS rows only, because they are the ones people are actually on. The feature releases in between (9.0, 9.1, 9.3–9.5, 10.0, 10.1) follow the identical two-year rule; every one of them is on the Confluence lifecycle page. Note the gap in the 7.x era: 7.13 died in August 2023, and anyone who moved to 7.19 got sixteen more months — then that died too. Every 7.x line has been unsupported since December 13, 2024.
Nine exploited CVEs and a ransomware flag
Confluence is not an ordinary case of “unsupported software carries risk.” It carries nine entries in CISA’s Known Exploited Vulnerabilities catalog — vulnerabilities with confirmed exploitation in the wild — and CISA flags the product for use in ransomware campaigns. The most recent additions, CVE-2023-22515, CVE-2023-22518 and CVE-2023-22527, were all mass-exploited against internet-facing Confluence servers within days of disclosure, and all three affected the 7.x and 8.x lines that are now out of support.
That history is the whole argument. An unpatched Confluence server is not a theoretical exposure waiting for a researcher; it is a target class that attackers already have working tooling for, and the versions people are still searching for are exactly the ones that tooling was built against. It is why the 7.13 score sits at 70 and only rises. Our Confluence CVE exposure analysis goes through the individual entries.
Which line to land on
If you are on 9.x or 10.x feature releases: move to 10.2 LTS. It is supported to December 2, 2027 — the longest runway available — and stays on the fix stream for its whole window.
If you are on 9.2 LTS: you are supported, but only until December 10, 2026 — four months. Going to 10.2 now avoids scheduling a second upgrade for the winter.
If you are on 8.5 or any 7.x: you have been unpatched since December 2025 at best, December 2024 for 7.19, and August 2023 for 7.13 — on a KEV-listed, ransomware-flagged product. This is not upcoming; it is overdue. From 7.x, Atlassian’s documented path is staged (7.19 LTS as the intermediate hop, then onward); from 8.5, 10.2 is a direct target. If a migration cannot start now, get the server off the public internet today and treat that as the compensating control it is, not a solution.
If you are on Confluence Server (not Data Center): Server ended entirely on February 15, 2024 — there is no supported Server release. Every Server install is out of support regardless of version; the options are Data Center or Cloud. Our Atlassian Server and Data Center guide covers that transition.
Every Confluence release, its dates and its EOL Risk Score are on the Confluence lifecycle page; the rest of the Atlassian stack is on the Atlassian vendor page.
Frequently Asked Questions
How long is a Confluence version supported?
Atlassian supports each Confluence Data Center release for two years after its initial feature or Long-Term Support release — to the day. Confluence 9.2 LTS, released December 9, 2024, ends December 10, 2026; Confluence 10.2 LTS, released December 2, 2025, ends December 2, 2027. There is no extended support tier from Atlassian.
Is Confluence 7.13 still supported?
No. Confluence 7.13 LTS reached end of life on August 17, 2023, and its final release was 7.13.20. Every 7.x line is now end of life — 7.19 LTS, the last of them, ended December 13, 2024. Anyone still on 7.13 is three LTS lines behind the current one and has received no security fixes for three years.
Which Confluence versions are supported right now?
As of mid-August 2026: 10.2 LTS (to December 2, 2027), 10.1, 10.0, 9.5, 9.4, 9.3, and 9.2 LTS (to December 10, 2026), plus 9.1 (to October 3, 2026). Everything 9.0 and earlier — including 8.5 LTS, which ended December 15, 2025 — is out of support.
Which Confluence version should I upgrade to?
10.2 LTS — supported to December 2, 2027, the longest runway available. 9.2 LTS is still supported but ends December 10, 2026, only four months out, so it schedules a second upgrade almost immediately. From 7.x, expect a staged path (7.19 LTS as the intermediate hop is Atlassian's documented route).