Confluence servers under attack as hackers exploit critical Apache Axis flaw CVE-2026-90436

Attackers are actively exploiting a critical flaw in the Apache Axis library to break into Atlassian Confluence servers, and organisations running the affected software should treat it as an emergency. The flaw, tracked as CVE-2026-90436, allows an unauthenticated attacker to run code on a vulnerable server, and it has already been used against Confluence Data Center and the IT management platform N-able N-central.
Rapid7 said it detected exploitation against a customer’s Confluence Data Center server on 13 November 2026, the same day N-able reported exploitation in the wild against N-central. Rapid7 published its findings on 16 November.
What is CVE-2026-90436?
CVE-2026-90436 is an unsafe reflection flaw, classed as CWE-470, in Apache Axis 1.x, a Java library for building SOAP web services. The Apache Software Foundation disclosed it on 6 November 2026. A crafted SOAP fault message can make Axis load and instantiate a Java class chosen by the attacker, which becomes remote code execution without any login. CISA scores the flaw 9.8 out of 10 under CVSS 3.1; Atlassian rates it 9.3 under CVSS 4.0.
Axis 1.x, up to version 1.4, has reached end of life, and Apache does not plan to publish a fixed Axis 1.x release. It recommends moving to another SOAP engine, such as Apache Axis 2, or applying its published patch commit.
How the Confluence attack unfolded
Rapid7’s account of the intrusion it observed shows how quickly the flaw can be turned into a full compromise. Its team first noticed a surge of alerts from abnormal processes launched by a Confluence server. The access logs showed unauthenticated POST requests to the SOAP endpoint at /plugins/servlet/soap-axis1/confluenceservice-v2, each returning an HTTP 500 error. Despite the error responses, the Confluence Java process began launching Bash and curl as the dedicated confluence service account within seconds.
The attacker then ran hundreds of hex-encoded shell commands fetched through Pinggy and Cloudflare Tunnel domains, enumerated the host and the Confluence configuration, and just over three minutes after the first exploit request was authenticating to MySQL using Confluence’s own database credentials, hunting through pages and attachments for credentials, tokens, VPN configurations and payment card numbers.
The attack continued for hours. About four hours in, the intruder had acquired a service account credential and begun querying a production cloud data warehouse, and roughly twelve hours after the first exploit request signed in to Microsoft 365 as an integration service account using legacy authentication from 192.238.253.176, the same address seen in the earlier exploit requests.
Which Confluence servers are at risk?
Atlassian’s security advisory, published on 9 November, says Confluence Data Center versions 1.x through 9.x are affected, but only when the “Remote API (XML-RPC & SOAP)” setting is enabled. That setting has been off by default for new installations since Confluence 3.0, and the feature was removed entirely in Confluence 10.0, so 10.x releases are not affected. Atlassian Cloud sites are unaffected.
The fixed release is Confluence Data Center 9.2.28. Organisations that cannot patch immediately should switch off the Remote API setting, which takes effect without restarting Confluence, although scripts, automations and third-party add-ons that rely on it may stop working. Check the mitigation by visiting the SOAP endpoint in a browser: a correctly mitigated server returns HTTP 403 Forbidden.
Atlassian says it cannot confirm whether any particular customer’s instances have been affected. Rapid7 has published the IP addresses behind the Confluence activity: 192.238.253.176, 5.133.47.243, 163.182.68.109 and 104.13.106.166.
N-able N-central also exploited
The same Axis flaw is the initial step in an attack chain against N-able N-central, where exploitation depends on the non-default Legacy API setting. A public proof-of-concept exploit targeting N-central appeared on 12 November, N-able reported in-the-wild exploitation the next day, and reporting cited by Censys says at least 21 production N-central servers were compromised. N-able released N-central 2026.4 HF3 on 16 November, which disables the Legacy API, and administrators are urged to upgrade on an emergency basis.
As of 17 November, CVE-2026-90436 had not been added to CISA’s Known Exploited Vulnerabilities catalogue, so organisations should not wait for that listing before acting. Anyone running Confluence Data Center or N-central should check whether the vulnerable settings are enabled, apply the vendor fixes now, and hunt through logs for the published indicators. Source: Rapid7. Second source: Censys advisory on CVE-2026-90436, which also links the Atlassian security advisory.
Frequently asked questions
Is my Confluence server affected by CVE-2026-90436? Only Confluence Data Center 1.x to 9.x with the “Remote API (XML-RPC & SOAP)” setting enabled. Confluence 10.x and Atlassian Cloud are not affected.
What is the fix? Upgrade to Confluence Data Center 9.2.28 or a current 10.x release. If patching must wait, disable the Remote API setting.
Has the flaw been exploited? Yes. Rapid7 detected exploitation against Confluence Data Center on 13 November 2026; N-able reported the same against N-central that day.