Hackers Actively Exploiting Atlassian Confluence RCE Vulnerability, 1.2M Instances Exposed to the Internet

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Hackers are actively exploiting a critical remote code execution (RCE) vulnerability in Atlassian Confluence Data Center that can let them run code without signing in.

Rapid7 detected exploitation in a customer environment on November 13, 2026, and is urging affected organizations to take emergency action rather than wait for routine patching.

Censys reported 1,212,568 internet-facing Confluence web properties in its November 16 advisory. However, this figure does not represent confirmed vulnerable installations or separate servers.

It counts hostname-and-port combinations where Confluence was detected, without checking the software version or whether the setting needed for exploitation was enabled.

Tracked as CVE-2026-90436, the flaw affects Apache Axis 1.x, a Java library used by Confluence’s XML-RPC and SOAP APIs. Atlassian rates the issue as critical, with a CVSS v4.0 score of 9.3. Exploitation requires the “Remote API (XML-RPC & SOAP)” setting to be enabled.

The weakness lies in how Axis processes specially crafted SOAP fault messages. An attacker can supply a Java class name that Axis loads before checking whether it belongs to the expected error type. Under suitable conditions, loading or creating that class can trigger code execution on the server.

Actively Exploited Confluence Flaw

This processing happens before service-level authentication checks run. As a result, authentication handlers attached to an affected service cannot stop the malicious request from reaching the vulnerable code path. Successful exploitation depends on a suitable class being available within the application.

Atlassian lists Confluence Data Center versions 1.x through 9.x as affected when the Remote API is enabled. The setting has been turned off by default for new installations since Confluence 3.0. Version 10.0 removed the feature entirely, and Atlassian Cloud sites are unaffected.

Hosts running Atlassian Confluence, counted by unique IP addresses rather than individual hostnames and ports (source : censys )
Hosts running Atlassian Confluence, counted by unique IP addresses rather than individual hostnames and ports (source: Censys )

Rapid7’s investigation confirms exploitation against Confluence, but does not describe the attacker’s later actions. Its published indicators include 192.238.253[.]176, 5.133.47[.]243, 163.182.68[.]109, and 104.13.106[.]166. Their absence from logs does not establish that a system escaped compromise.

The same Axis flaw also provides initial access in the N-able N-central 4EverAble2Shell exploit chain. That chain requires Legacy API access and combines code execution with a separate privilege escalation weakness. Those additional steps should not be assumed to apply to Confluence.

Earlier Confluence attacks linked to LockBit ransomware involved CVE-2023-22527, a different vulnerability. They provide background on the risks facing exposed collaboration servers, not evidence of ransomware deployment through this newly reported flaw.

Atlassian’s advisory identifies Confluence Data Center 9.2.28 as a fixed release. Administrators should upgrade to that build or an unaffected release. Where patching must wait, disabling the Remote API under General Configuration and Further Configuration provides temporary protection.

The change takes effect without restarting Confluence, although older integrations may stop working. Administrators can verify the mitigation by checking that /plugins/servlet/soap-axis1/confluenceservice-v2 returns HTTP 403. Previously exposed systems still require investigation to determine whether they were compromised.

Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs

The post Hackers Actively Exploiting Atlassian Confluence RCE Vulnerability, 1.2M Instances Exposed to the Internet appeared first on Cyber Security News.