Confluence 7.13 Release Notes, Release Date and End of Life

By Scott Bissett  ·  Published: September 20, 2026  ·  Reference guide  ·  Release dates read from Atlassian's Confluence 7.13 release notes on the day of publication.

Confluence 7.13 was released on August 17, 2021 as a Long Term Support release, and it reached end of life on August 17, 2023. Its final bug fix release is 7.13.20. If you are looking up the 7.13 release notes because you run it, the most important line is not in them: 7.13 has had no bug fixes and no security fixes for more than three years. The official notes are on Atlassian's Confluence 7.13 Release Notes page; this guide summarises them, dates every 7.13.x release, and sets out where to go next.

What the 7.13 release notes covered

Atlassian's page has four parts. In our words:

• Long Term Support release roundup. 7.13 followed 7.4, the previous Long Term Support release, by more than a year. The notes roll up what arrived in between, mostly for Data Center: more audit log events, single sign-on with OpenID, access logging switched on by default, webhooks and personal access tokens for integrations, and analytics for page views and edits.
• Security check-up. A checklist Atlassian suggests running at upgrade time: subscribe to security advisory alerts, keep technical contacts current, run Confluence as a dedicated non-root user, and review the rest of its hardening advice.
• Resolved issues. One section per bug fix release, 7.13.0 through 7.13.20, each with its release date and a list of the issues fixed.
• Get ready to upgrade. A pointer to the 7.13 upgrade notes and the standard upgrade instructions.

The notes also explain what Long Term Support meant: Atlassian would keep shipping bug fix releases for 7.13 until it reached end of life, covering critical security, stability, data integrity and performance issues. That promise ran out on August 17, 2023.

Every Confluence 7.13.x release, with Atlassian's date

Release days are the ones Atlassian gives in the release notes. Some third-party trackers show these releases a day or two earlier; we follow the vendor's page, and our build re-reads it to check the first and last dates.

Security: what 7.13 did and did not get fixed

• CVE-2021-26084 (remote code execution, exploited in the wild): fixed from 7.13.0, so every 7.13 release has the fix.
• CVE-2022-26134 (remote code execution, exploited in the wild): fixed in 7.13.7. A 7.13 server on 7.13.6 or older is still exposed to it.
• CVE-2023-22518 (improper authorization, exploited in the wild and used by ransomware): disclosed in late 2023, after 7.13 had reached end of life. Atlassian's fixed releases were 7.19.16 and several 8.x releases. There is no fixed 7.13 release, and there will not be one.

That third entry is what end of life means in practice. Even a fully patched 7.13.20 server carries a known, exploited flaw that the vendor fixed only on newer lines, and the same holds for anything found since. Our Confluence CVE exposure analysis goes through the entries one by one, and the Exploited and Unpatchable feed tracks exploited flaws that have no fix on end-of-life versions.

Where to go from 7.13

Atlassian retires each Confluence version two years after its release, Long Term Support lines included. These are the Long Term Support lines since 7.13:

1. Pick the newest Long Term Support line, not the nearest one. 9.2 is supported today but ends on December 10, 2026; landing there books a second upgrade almost at once. 10.2 runs to December 2, 2027.
2. Expect a staged path from 7.13. Check Atlassian's upgrade documentation for the supported route from your exact release, and the supported platforms for the target: the Java version and the database versions both move between 7.13 and the current lines.
3. Check your licence type. Atlassian ended support for its Server products in February 2024, and the banner on its own documentation now says Data Center support ends in March 2029. Our Atlassian Server and Data Center end of life guide covers what that means for where you upgrade to.
4. If the upgrade cannot start now, take the server off the public internet today. That is a stopgap, not a fix.

Frequently Asked Questions

Related

• Confluence 7.13 — live status and EOL Risk Score
• Confluence end of life: every version's date and which to land on
• Confluence CVE exposure
• Atlassian Server and Data Center end of life
• Confluence — every version