Cybersecurity Data Breach Hacking and Exploits Server and Virtualisation

Atlassian Confluence exploitation prompts emergency action

Atlassian Confluence exploitation prompts emergency action

Hackers are actively exploiting a critical remote code execution flaw 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.

What the Confluence flaw allows

Tracked as CVE-2026-90436, the weakness affects Apache Axis 1.x, the Java library used by Confluence’s XML-RPC and SOAP APIs. Atlassian rates it critical and gives it a CVSS v4.0 score of 9.3. Exploitation depends on the “Remote API (XML-RPC & SOAP)” setting being enabled.

The flaw sits in the way Axis handles specially crafted SOAP fault messages. An attacker can provide a Java class name that Axis loads before it checks whether the class belongs to the expected error type. Under suitable conditions, that loading or class creation can lead to code execution on the server. This processing happens before service-level authentication checks run, so authentication handlers attached to an affected service cannot stop the malicious request from reaching the vulnerable code path.

Exposure and affected versions

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

Censys reported 1,212,568 internet-facing Confluence web properties in its November 16 advisory. That number 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.

What Rapid7 and Atlassian published

Rapid7 says its investigation confirms exploitation against Confluence, but it does not describe the attacker’s later actions. Its published indicators are 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.

Atlassian’s advisory identifies Confluence Data Center 9.2.28 as a fixed release. Administrators are told to upgrade to that build or to an unaffected release. If patching must wait, disabling the Remote API under General Configuration and Further Configuration provides temporary protection. The change takes effect without restarting Confluence, though older integrations may stop working. Administrators can confirm the mitigation by checking that /plugins/servlet/soap-axis1/confluenceservice-v2 returns HTTP 403.

Related attack chains and earlier cases

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

Earlier Confluence attacks tied to LockBit ransomware involved CVE-2023-22527, a different vulnerability. They offer background on the risks facing exposed collaboration servers, but they do not show ransomware deployment through this newly reported flaw. Previously exposed systems still need investigation to determine whether they were compromised.

Leave a Reply

Your email address will not be published. Required fields are marked *

🧰

Free Tools: IP, DNS, SSL

40+ free network and other tools in one place. No signup. Click explore or visit https://technochat.in/tools

Explore