Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.
On November 13, 2026, Rapid7 MDR detected active exploitation of CVE-2026-90436 against Atlassian Confluence Data Center in a customer environment. The vulnerability, an unsafe reflection flaw (CWE-470) in the Apache Axis 1.x SOAP parser, enables unauthenticated remote code execution and carries a CVSS 9.8 Critical rating from CISA-ADP. Both affected products — Confluence Data Center and N-able N-central — require non-default configuration to be vulnerable. Apache Axis 1.x remains end-of-life, and the project has explicitly stated it will not release a corrective update.
- Active exploitation detected November 13, 2026 by Rapid7 MDR against Confluence Data Center, with unauthenticated POST requests to the
/plugins/servlet/soap-axis1/confluenceservice-v2endpoint - Apache Axis 1.x is end-of-life: the project will not release official patches for CVE-2026-90436, according to the CVE record
- Both affected products (Confluence Data Center and N-able N-central) require non-default configuration to be vulnerable
- The attacker obtained service account credentials roughly 4 hours after initial exploit; tooling structure suggests AI-assisted automation per Rapid7
- At roughly 12 hours, the attacker signed into Microsoft 365 as an integration service account using legacy authentication from IP 192.238.253[.]176
The Mechanism: Reflection Before Authentication
CVE-2026-90436 exploits an unsafe reflection in the Apache Axis 1.x SOAP parser. A SOAP Fault message containing an <exceptionName> element triggers the loading and instantiation of arbitrary classes on the Java classpath. This loading occurs before the SOAP service authentication handlers execute, bypassing endpoint-level protections.
Atlassian Confluence Data Center exposes this behavior via the /plugins/servlet/soap-axis1/confluenceservice-v2 endpoint, which accepts unauthenticated input. Rapid7 observed POST requests to this endpoint returning HTTP 500 responses; despite the error code, the Confluence Java process spawned Bash and curl child processes within seconds, indicating successful payload execution.
MDR Detection and Incident Timeline
Rapid7 logs trace a structured, rapid attack within the single monitored environment. Approximately 3 minutes after the first exploit request, the attacker authenticated to MySQL using credentials extracted from the Confluence configuration, then queried page bodies, application links, and attachments.
Scripts parsed Office documents and applied Luhn checks to identify payment card numbers. They also used Confluence application credentials to query the internal Atlassian Crowd API and attempted AS-REP roasting with Impacket GetNPUsers.py against the domain controller, without success according to Rapid7.
At roughly 4 hours post-exploit, the attacker obtained service account credentials and began querying a production cloud data warehouse. At roughly 12 hours, the attacker signed into Microsoft 365 as an integration service account using legacy authentication from IP 192.238.253[.]176.
"On November 13, 2026, Rapid7 MDR detected exploitation of CVE-2026-90436 against Atlassian Confluence Data Center in a customer environment." — Rapid7 Emergent Threat Response
Signatures of Automation
A distinctive element of the attack is the shell command structure: hex-encoded, with labeled delimiters and sequential task IDs. According to Rapid7 analysis, this structure suggests the use of AI-assisted tooling that manages remote execution in a modular, traceable fashion.
The use of ephemeral infrastructure — Pinggy domains and Cloudflare tunnels — allowed payload fetch without exposing directly attacker-controlled servers. The operational speed and systematic enumeration observed in this incident indicate a threat actor capable of maximizing impact within compressed timeframes.
N-able N-central: Same Root, Different Target
On November 13, 2026, within the same timeframe as the Confluence exploitation, N-able reported in-the-wild attacks against N-central for a vulnerability strongly correlated with CVE-2026-90436. A proof-of-concept exploit was published November 12, 2026 as part of public zero-day disclosures. Like Confluence, N-central requires non-default configuration to expose the vulnerable attack surface, according to Rapid7.
The correlation between the two products, both built on end-of-life Axis 1.x, highlights the risk for organizations maintaining legacy SOAP engines in non-standard configurations. This represents a shared dependency on an abandoned component that remains active for backward compatibility.
The EOL Wall: Why Axis Gets No Patch
The CVE record states explicitly: "The Apache Axis project does not expect to create an Axis 1.x release fixing this problem." The official recommendation is migration to an alternative SOAP engine, an architectural undertaking that admits no quick fix.
Organizations running Confluence Data Center or N-central in non-default configuration face complex choices: apply any updates provided by the downstream product vendors, or remove or disable the vulnerable SOAP endpoint where the functionality is not essential.
Immediate Actions
For Confluence Data Center, verify whether the /plugins/servlet/soap-axis1/confluenceservice-v2 endpoint is active and whether the configuration includes the SOAP Axis 1.x plugin in non-default mode. If the service is not required, disabling it reduces the attack surface without waiting for intervention on the EOL component.
For N-able N-central, consult the vendor advisory from November 13, 2026 and evaluate removal of the configuration that exposes the vulnerable SOAP parser. The PoC published November 12, 2026 makes exploitation reproducible and increases the likelihood of automated attacks.
In Confluence logs, search for POST requests to the SOAP endpoint returning HTTP 500 followed by anomalous child processes (Bash, curl, wget) spawned from the server Java process. The presence of this sequence indicates successful exploitation despite the error code.
For teams managing M365 integrations with legacy authentication, monitor sign-ins from suspicious IPs such as 192.238.253[.]176 and verify whether service accounts connected to Confluence or Crowd have triggered unexpected authentications. Enforcing conditional access and disabling legacy protocols reduces the risk of reuse for compromised credentials.
Editorial Close
CVE-2026-90436 combines three high-risk elements: an end-of-life component with no prospect of a fix, a CVSS 9.8 exploit that bypasses authentication, and a documented post-exploitation chain that moves from RCE to cloud access in under a day. The case detected by Rapid7 shows how non-default configuration — often enabled for backward compatibility or legacy integrations — becomes the entry point for structured, automated attacks. The absence of patches for Axis 1.x shifts the protection burden entirely to operators of downstream products: verify active endpoints, remove what is not needed, and treat every anomalous SOAP request as a potential compromise already in progress.
Sources
Get DeafLetter
A weekly selection of signals, vulnerabilities and guides. Critical alerts remain optional.
You can unsubscribe at any time. Privacy policy.