How severe is CVE-2023-22518?

CVE-2023-22518 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2023-22518?

Affected package information for CVE-2023-22518 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2023-22518?

Apply the atlassian confluence data center security patch or hotfix for CVE-2023-22518 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2023-22518 across my infrastructure?

Inventory every atlassian confluence data center deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2023-22518 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2023-22518?

O3 detects and blocks CVE-2023-22518 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2023-22518 actively exploited in the wild?

Yes. There are 12 known exploit references for CVE-2023-22518, including 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-22518?

CVE-2023-22518 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2023-22518 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-22518 (Atlassian Confluence Data Center and Server Improper Authorization Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-11-07. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-11-28. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2023-22518?

CVE-2023-22518 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2023-22518?

CVE-2023-22518 affects atlassian confluence data center (1 version, e.g. 8.6.0); atlassian confluence server (1 version, e.g. 8.6.0). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2023-22518?

A Nuclei detection template exists for CVE-2023-22518, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2023-22518, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-22518 published, and has it been updated?

CVE-2023-22518 was published on October 31, 2023 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-11-07 — agencies required to remediate by 2023-11-28 · Ransomware

CVE-2023-22518

CRITICAL

All versions of Confluence Data Center and Server are affected by this unexploited vulnerability. This Improper Authorization vulnerability allows an unauthenticated attacker to reset…

Published

Oct 31, 2023

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

12 known

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

All versions of Confluence Data Center and Server are affected by this unexploited vulnerability. This Improper Authorization vulnerability allows an unauthenticated attacker to reset Confluence and create a Confluence instance administrator account. Using this account, an attacker can then perform all administrative actions that are available to Confluence instance administrator leading to - but not limited to - full loss of confidentiality, integrity and availability.

Atlassian Cloud sites are not affected by this vulnerability. If your Confluence site is accessed via an atlassian.net domain, it is hosted by Atlassian and is not vulnerable to this issue.

Affected Products

2 products · 10 configurations

Application

confluence data centeratlassian

≥ 8.5.0 && < 8.5.3

1 version

8.6.0

Application

confluence serveratlassian

≥ 8.5.0 && < 8.5.3

1 version

8.6.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.