1-minute read of a 4 min report

Attackers Exploit Confluence Remote API Flaw to Run Code

By

1-minute read

What a defender needs to know

Rapid7’s managed detection team observed exploitation of CVE-2026-90436 against a customer’s Atlassian Confluence Data Center on November 13. Apache Axis 1.x through 1.4 can load a class named by an inbound SOAP fault before service-level authentication runs. A suitable class on the application classpath makes remote code execution possible without authentication.

Check internet-accessible Confluence Data Center first, then internally reachable servers. CISA added the issue to KEV on November 18; NVD lists November 21 as the action date for covered federal agencies. Rapid7 says versions 1.x through 9.x are exposed when Remote API (XML-RPC & SOAP) is enabled. In General Configuration → Further Configuration, read that setting and the installed release. Upgrade to fixed 9.2.28 or a current unaffected 10.x release. If patching waits, clear the Remote API setting and save; the change takes effect without a restart, but integrations using the API may stop working. Confirm the setting is off and check those integrations. Confluence 10.x removed the feature, and Atlassian Cloud is unaffected.

For exposed servers, correlate POST/HTTP 500 at /plugins/servlet/soap-axis1/confluenceservice-v2 with Confluence Java child processes; preserve logs and check Rapid7’s addresses: 192.238.253[.]176, 5.133.47[.]243, 163.182.68[.]109, 104.13.106[.]166. Investigate child processes, database and attachment access; other addresses can evade an IP-only search. Rapid7 reports N-central exploitation: upgrade to 2026.4 HF3 (2026.4.1.39), which disables Legacy API; verify its setting afterward.

Primary sources