Safeguard
Vulnerability Analysis•

CVE-2023-22512: High DoS in Atlassian Confluence

An unauthenticated attacker can take a Confluence Data Center or Server instance offline. High, CVSS 7.5. Upgrade to 7.19.14, 8.5.1 or 8.6.0 or later.

Safeguard Security Team
3 min read

CVE-2023-22512 is a high severity denial of service flaw (CVSS 7.5) in Confluence Data Center and Server, introduced in version 5.6. An unauthenticated attacker can disrupt a vulnerable instance over the network. Atlassian fixed it in 7.19.14, 8.5.1 and 8.6.0, so upgrade to one of those or later.

What's affected

  • Confluence Data Center and Server from version 5.6 up to the fixed releases, per Atlassian.
  • The September 2023 security bulletin lists the affected range as 5.6 or later and below 7.19.13 in the 7.19 line, plus below 8.5.1 and below 8.6.0.
  • Fixed versions: 7.19.14, 8.5.1, 8.6.0. The Jira ticket CONFSERVER-91258 lists the same three fix versions.
  • Severity: CVSS 3.1 score 7.5 High, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Availability is the only impact.

One wording difference is worth knowing. The bulletin table lists "below 7.19.13" as the affected range in the 7.19 line, while the advisory text says to upgrade to 7.19.14 or later. Aim for 7.19.14 or later and you satisfy both.

How to check if you're exposed

Confluence reports its own version, so start there. Open the Confluence administration area and look at the system information page, or read the version in the page footer.

If you manage the host, you can also read the version from the install directory:

grep -i "confluence-version" /opt/atlassian/confluence/confluence/META-INF/MANIFEST.MF

Adjust the path to your install location. Compare what you see with the fixed releases above. Anything from 5.6 up to 7.19.13, or on the 8.x line below 8.5.1, needs an upgrade.

What to do now

  1. Find every Confluence Data Center and Server instance, including test and legacy ones.
  2. Read the version of each and compare it with 7.19.14, 8.5.1 and 8.6.0.
  3. Upgrade to a fixed release, or to the latest release for your support line. Atlassian recommends the latest version where you can.
  4. If you cannot upgrade at once, limit network access to the instance to trusted ranges while you plan the change.
  5. Watch instance health and request rates for abnormal spikes until the upgrade is complete.

Why it matters

The weakness is uncontrolled resource consumption (CWE-400 (Uncontrolled Resource Consumption)). A request can make the application use more of a scarce resource than it should, until legitimate users can no longer be served. Atlassian says the attacker needs no account and no user interaction.

A wiki outage is rarely a data breach, but teams rely on Confluence for runbooks, incident pages and documentation, which are the pages you want during an incident. The ticket labels the finding as coming from Atlassian's Bug Bounty program. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Does this let an attacker read or change pages?

No. The vector shows no confidentiality or integrity impact, only high availability impact.

Is Confluence Cloud affected?

The advisory names Confluence Data Center and Server. Atlassian manages Cloud for you.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.