Skip to content
The Cybersecurity Focus
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

The Cybersecurity Focus

Cybersecurity news, threat intelligence, and vulnerability research.

  • Home
  • Home
CVEexploitRCEVulnerability

Apache Axis RCE Exploited in Confluence Data Center

By ogwatermelon
November 18, 2026 5 Min Read
0
November 17, 2026

The CVE-2026-90436 Apache Axis remote code execution flaw is now being actively exploited against Atlassian Confluence Data Center and N-able N-central servers. Rapid7 detected real intrusions on November 13, 2026, and the attackers reached Microsoft 365 and a production cloud data warehouse within hours. Organizations running SOAP-enabled Confluence instances need to patch or disable the Remote API immediately.

What Happened: CVE-2026-90436 Apache Axis RCE Exploited in Confluence

On November 6, 2026, the Apache Software Foundation disclosed CVE-2026-90436, a critical unsafe reflection vulnerability in Apache Axis 1.x. CISA scored the flaw at 9.8 Critical under CVSS v3.1. The bug allows unauthenticated remote code execution through crafted SOAP fault messages.
Rapid7’s managed detection and response team confirmed active exploitation on November 13, 2026, against a customer running Atlassian Confluence Data Center. N-able reported exploitation against N-central appliances on the same day for a vulnerability that strongly correlates with the same root cause. A public proof-of-concept exploit targeting N-central appeared on November 12 as part of the Able2Shell disclosure series.
Consequently, Rapid7 now recommends remediating exposed systems on an emergency basis, outside normal patching cycles.

Technical Details of the Apache Axis CVE-2026-90436 RCE Flaw

The vulnerability is an unsafe reflection issue classified as CWE-470 in Apache Axis. The Axis runtime handles inbound SOAP fault messages by loading the class name supplied inside the fault and instantiating it, before confirming that the object is actually an AxisFault. Because class loading alone executes static initializer code, an attacker only needs a suitable class on the application classpath to reach code execution.
Axis parses the fault before it performs any per-service authorization check, so no valid credentials are required. The attack path looks like this:

  • Entry point: Unauthenticated POST requests to the SOAP endpoint, such as /plugins/servlet/soap-axis1/confluenceservice-v2 on Confluence
  • Trigger: A crafted SOAP fault containing an attacker-chosen class name for remote instantiation
  • Execution: The Java process launches child processes such as bash and curl under the product service account
  • Exploitation: Attackers download staged scripts over temporary tunnels and begin host and network enumeration

Interestingly, the exploit requests in the observed intrusion returned HTTP 500 errors. Despite those error responses, the Confluence Java process still spawned Bash and curl within seconds of each request.

Observed Intrusion Timeline

Rapid7 telemetry shows the attack progressing with remarkable speed. Roughly three minutes after the first execution, the attacker authenticated to MySQL using Confluence’s own database credentials and queried page bodies, application links, and attachments. Four hours in, the attacker held a service account credential and was querying a production cloud data warehouse.
About twelve hours after the first exploit request, the attacker signed in to Microsoft 365 as an integration service account using legacy authentication from 192.238.253[.]176. That same address appeared in the hostname of the attacker’s Pinggy tunnel. The commands ran hex-encoded with labeled delimiters and sequential task IDs, a pattern that suggests AI-assisted automated tooling.

Indicators of Compromise

Security teams should hunt for the following infrastructure associated with Confluence exploitation:

  • IP addresses: 192.238.253[.]176, 5.133.47[.]243, 163.182.68[.]109, 104.13.106[.]166
  • Domains: *.trycloudflare[.]com, wpefh-192-238-253-176.free.pinggy[.]net, webhook[.]site

N-able listed 157.20.241[.]16, 139.99.69[.]109, and 79.76.51[.]56 for N-central customers who had not disabled the Legacy API. Note that the absence of these indicators does not confirm an environment was clean.

Business and Operational Impact

The CVE-2026-90436 Apache Axis RCE carries severe consequences because the entry point requires no authentication and the affected library is embedded inside widely deployed enterprise products.

  • Direct server takeover with code execution as the Confluence service account on exposed instances
  • Credential exposure harvested from Confluence page content, attachments, and application links
  • Cloud identity compromise through stored service account credentials reaching Microsoft 365 and data warehouses
  • Payment card and financial data risk from attackers parsing uploaded Office documents and applying Luhn checks to locate card numbers
  • Domain escalation attempts using Impacket’s GetNPUsers.py for AS-REP roasting against domain controllers
  • Supply chain risk for any custom Java application still running Apache Axis 1.x, which reached end of life with no planned fixed release

Atlassian states clearly that it cannot confirm whether any given instance was compromised. Organizations must investigate exposed servers themselves, even after patching.

Mitigation and Recommendations

Apache Axis 1.x is end of life, and the Apache Software Foundation will not publish a fixed 1.x release. Instead, Apache recommends migrating to another SOAP engine such as Apache Axis 2, or applying the upstream patch commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd to an Axis 1.x build.

Immediate Actions for Defenders

  1. Upgrade every Atlassian Confluence Data Center instance to version 9.2.28 or a current 10.x release
  2. If patching must wait, clear the “Remote API (XML-RPC and SOAP)” checkbox under General Configuration and Further Configuration
  3. Validate the mitigation by browsing to /plugins/servlet/soap-axis1/confluenceservice-v2, which should return HTTP 403 Forbidden
  4. Upgrade N-central appliances to N-central 2026.4 HF3 (2026.4.1.39), released November 16, 2026, which disables the vulnerable Legacy API
  5. Restrict management interface exposure with firewall rules and VPN for both Confluence and N-central servers
  6. Audit in-house Java applications for Apache Axis 1.x dependencies and migrate or patch them

Hunting for Compromise

Run these checks against any instance that was reachable with the SOAP APIs enabled:

  • Search access logs for unauthenticated POST requests to the SOAP servlet endpoint returning HTTP 500
  • Look for abnormal child processes spawned by the Confluence Java process under the service account
  • Review outbound connections to Pinggy, Cloudflare Tunnel, and webhook[.]site infrastructure
  • Rotate all credentials and application links stored inside Confluence pages and attachments
  • Audit Microsoft 365 sign-ins for legacy authentication from the listed IP addresses
  • Check for unauthorized MySQL queries against the Confluence database by the application account

Bottom line: The CVE-2026-90436 Apache Axis remote code execution vulnerability is confirmed as exploited against Confluence Data Center, and a full intrusion chain reached Microsoft 365 within a single day. Treat this as an emergency, and patch or disable the Remote API on every affected server today.

Incident Summary

CVE ID: CVE-2026-90436 (CVSS 9.8 Critical, CWE-470)
Root Cause: Unsafe reflection in Apache Axis 1.x when handling inbound SOAP fault messages
Affected Products: Atlassian Confluence Data Center 1.x through 9.x with Remote API enabled; N-able N-central with Legacy API enabled; Apache Axis 1.x through 1.4 generally
Unaffected: Confluence 10.x and later, and all Atlassian Cloud sites
Disclosure Date: November 6, 2026 (Apache), advisory published November 9, 2026 (Atlassian)
Confirmed Exploitation: November 13, 2026 (Rapid7 MDR and N-able)
Patch Status: Available: Confluence 9.2.28, N-central 2026.4 HF3, and Apache Axis patch commit 41f3b4e8
Impact Observed: Code execution as service account, MySQL and Confluence credential theft, Microsoft 365 sign-in, data warehouse access

References

  1. Rapid7, “Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited,” November 17, 2026, https://www.rapid7.com/blog/post/etr-rapid7-detected-exploitation-of-cve-2026-90436-against-atlassian-confluence-data-center-n-able-n-central-also-exploited/
  2. Atlassian, “CVE-2026-90436 – Remote Code Execution in Confluence Data Center,” November 9, 2026, https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html
  3. SecurityOnline, “CVE-2026-90436: Confluence Data Center RCE Actively Exploited, Patch Now,” November 16, 2026, https://securityonline.info/confluence-data-center-rce-cve-2026-90436/
  4. Apache Software Foundation, “Axis 1.x patch commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd,” https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd
  5. N-able, “N-central 2026.4 HF3 Release Notes,” November 16, 2026, https://status.n-able.com/2026/11/16/n-central-2026-4-hf3-release-notes/
  6. National Vulnerability Database, “CVE-2026-90436,” https://nvd.nist.gov/vuln/detail/CVE-2026-90436

Tags:

CVEExploitRCEVulnerability
Author

ogwatermelon

Follow Me
Other Articles
Previous

California Sues OpenAI Over AI Agents Escaping Sandboxes

Next

Java4Shell Critical Pre-Auth RCE in Jira, Jenkins, and Keycloak

AI Android Backdoor Botnet Breach Cloud CVE Exploit Hack Incident Infostealer KEV Linux Mac Malware Network News Phishing Ransomware RCE supp supply chain Virtualization Vishing Vulnerability Windows World Worm Zero Day

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026

Categories

  • AI
  • Android
  • Apple
  • Backdoor
  • BotNet
  • Breach
  • Cloud
  • CVE
  • exploit
  • Hack
  • Incident
  • Infostealer
  • KEV
  • Linux
  • Mac
  • Malware
  • News
  • Phishing
  • Ransomware
  • RCE
  • supply-chain
  • Uncategorized
  • Virtualization
  • Vishing
  • Vulnerabilities
  • Vulnerability
  • Windows
  • World
  • Worm
  • Zero Day
Copyright 2026 — The Cybersecurity Focus. All rights reserved.