Critical Atlassian Confluence Flaw Under Active Attack — 1.2M Exposed

Administrators of Atlassian Confluence Data Center must act immediately: a critical remote code execution (RCE) vulnerability—CVE-2026-90436—is being actively exploited in real-world environments. The flaw allows unauthenticated attackers to run arbitrary code, bypassing normal security checks, when specific settings are enabled.

What’s at Stake

The vulnerability arises from Apache Axis 1.x, a Java library used by Confluence’s XML-RPC and SOAP APIs. When a specially crafted SOAP fault message is processed, Axis may load a Java class supplied by the attacker without verifying its type. If that class either already exists or can be created in the application, the attacker gains full remote code execution on the server without needing to log in. This takes place before service-level authentication is enforced—making it far more dangerous. Organisations using Confluence versions 1.x through 9.x are affected, but only if the “Remote API (XML-RPC & SOAP)” setting is enabled. Version 10.0 has removed the vulnerable functionality, and cloud installations are not exposed.

How Big Is the Exposure?

As of November 16, internet scanning by Censys flagged 1,212,568 Confluence host-port combinations exposed to the internet. This raw count includes multiple entries per server and does not confirm whether a given instance is vulnerable or configured for API access. It identifies only that Confluence was detectable at those endpoints. Meanwhile, cybersecurity firm Rapid7 observed exploitation activity on November 13, 2026, in at least one customer environment. The firm urges emergency patching rather than waiting for routine maintenance.

Protection Measures & Mitigation

Atlassian has released version 9.2.28—among others that are safe from this issue. Administrators should upgrade immediately. If a full upgrade isn’t feasible right now, disabling the Remote API option under General Configuration → Further Configuration serves as a stopgap defense. This mitigation takes effect immediately and doesn’t require restarting the system—though some older integrations may break. To confirm that the protection is in place, checking that the endpoint /plugins/servlet/soap-axis1/confluenceservice-v2 responds with HTTP 403 is recommended. Any exposed systems need to be reviewed for signs of post-compromise activity.

Background & Broader Risks

This is not the first time exposed collaboration platforms have been a vector for serious attacks. Previous incidents such as attacks using a different Confluence vulnerability (CVE-2023-22527) have been linked with LockBit ransomware. While the current exploit chain does not necessarily involve ransomware or privilege escalation beyond the RCE, the mere presence of this kind of access puts victims at high risk.

For many organisations, the Remote API feature has been off by default since Confluence 3.0; new instances do not enable it automatically. Nonetheless, many legacy setups may still have it active, making them vulnerable. Cloud-hosted Confluence services are not impacted, as the feature is not present in those environments.

Analytical Take

This vulnerability underscores a recurring pattern: legacy features that persist in software long after they outlive their original purpose can become powerful attack vectors. The speed of current exploitation amplifies the stakes—every organization running Confluence Data Center with XML-RPC/SOAP enabled should assume exposure. The window for response is narrow: patch immediately, disable risky settings as needed, audit systems to detect breaches, and review feature settings in other legacy apps similarly built on outdated components. What you don’t know today could be what you regret in a cyber crisis tomorrow.