Confluence 6.7 · Version Status
Confluence 6.7 End of Life Date
Confluence 6.7 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Confluence 6.7 is past end of life. This version no longer receives security patches. 2473 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 30, 2020
2473 days past EOL
Latest Release
6.7.3
Standard release
Release Date
Jan 30, 2018
Confluence 6.7 series
Where these dates come from
End of lifeJan 30, 2020endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJan 30, 2018Vendor's own page (our correction) · confluence.atlassian.com · checked Oct 29, 2026medium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Confluence 6.7 was released on January 30, 2018 and support ended on January 30, 2020 — a supported lifespan of 2 years, in line with the 2 years median for Confluence releases. It was not an LTS release; Confluence reserves longer patch windows for its LTS releases. Its latest release on record is 6.7.3, published April 30, 2018 — 1 year and 9 months before support ended. It has been past its end-of-life date for 6 years and 9 months. 38 newer Confluence releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
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 → ·
View score card →
Extended Support
Extended Confluence 6.7 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
1.0.3a |
Supported |
EOL |
| 1.1 |
1.1.2 |
Supported |
EOL |
| 1.2 |
1.2.3 |
Supported |
EOL |
| 1.3 |
1.3.6 |
Supported |
EOL |
| 1.4 |
1.4.4 |
Supported |
EOL |
| 2.0 |
2.0.3 |
Supported |
EOL |
| 2.1 |
2.1.5 |
Supported |
EOL |
| 2.2 |
2.2.10 |
Supported |
EOL |
What does Confluence 6.7 end of life mean?
When Confluence 6.7 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Confluence 6.7 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Confluence 11.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Confluence 6.7 reach end of life?
Confluence 6.7 reached end of life on January 30, 2020. This version is no longer receiving security patches.
Is Confluence 6.7 still supported?
No. Confluence 6.7 reached end of life on January 30, 2020 and is no longer receiving security patches.
What should I upgrade to from Confluence 6.7?
The recommended upgrade from Confluence 6.7 is
Confluence 11.0 — the latest actively supported version. Check the
Confluence full timeline for all supported versions.
What are the security risks of running Confluence 6.7 past EOL?
Since Confluence 6.7 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Confluence should migrate immediately or implement compensating controls.