Rapid7’s managed detection team saw attackers exploit a Confluence Data Center server through a flaw in Apache Axis, an old SOAP library Confluence uses for its XML-RPC and SOAP API. The attack, on November 13, needed no login.
Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.
Only servers with “Remote API (XML-RPC & SOAP)” switched on are exposed. That setting has been off by default for new installs since Confluence 3.0, but older sites and anything with scripts or add-ons that use the API often still have it on. Atlassian’s fix is version 9.2.28, and the setting can be switched off without a restart.
Attackers are using an Apache Axis flaw (CVE-2026-90436) against self-hosted Confluence with the Remote API on. Switch off “Remote API (XML-RPC & SOAP)” today, then update to 9.2.28.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Attackers are hitting Confluence servers with the old Remote API on
Apache disclosed CVE-2026-90436 on November 6. When a SOAP fault message names an exception class, Axis 1.x loads that class and can create it before checking what it is. With a suitable class on the server, that leads to code execution. Axis 1.x reached end of life long ago and Apache does not plan a fixed release.
- Confluence: Atlassian’s advisory (November 9, 10 PM Pacific) lists Data Center 1.x through 9.x as affected when Remote API is enabled. Fixed in 9.2.28. Confluence 10.0 removed the feature, and Atlassian Cloud is not affected.
- Exploitation: Rapid7 detected it against Confluence in a customer environment on November 13 and published four attacker IP addresses on November 16.
- N-central: N-able reported attacks on November 13 that Rapid7 says strongly correlate with this same Axis flaw, on servers with the Legacy API on. We covered the earlier N-central attacks on November 11.
Self-hosted Confluence 9.x and older with XML-RPC and SOAP enabled
Confluence is where teams keep runbooks, architecture notes and, too often, passwords. Code running as the Confluence service can read all of it and reach the database behind it. Atlassian stopped supporting Confluence Server in February 2024, so old Server installs on these versions should be treated as exposed too.
CISA has not added CVE-2026-90436 to its exploited catalog yet; its latest update was November 13. Rapid7 calls for emergency remediation outside normal patch cycles, and we count this as confirmed exploitation.
Turn off Remote API now, then update to 9.2.28 or 10.x
- As a Confluence admin, open General Configuration, then Further Configuration (or
/admin/viewspacesconfig.action), click Edit, and clear “Remote API (XML-RPC & SOAP)”. The change takes effect on Save, no restart needed. - Check the mitigation:
<base_url>/plugins/servlet/soap-axis1/confluenceservice-v2should return HTTP 403 Forbidden. - Update to Confluence Data Center 9.2.28 or a current 10.x release. Expect any script, automation or add-on that used the SOAP or XML-RPC API to need a new method.
- If the setting was on and the site was reachable from the internet, investigate before you call it fixed. Rapid7 recommends checking exposed systems for signs of compromise.
Forward this
For whoever runs our Confluence wiki: attackers are breaking into self-hosted Confluence servers through an old API setting called Remote API (XML-RPC & SOAP). If we host Confluence ourselves, can someone check that setting today, switch it off, and plan the update to 9.2.28? If we use Atlassian Cloud, we are not affected.
Details
- CVE-2026-90436: unsafe reflection / deserialization of an inbound SOAP fault in Apache Axis 1.x (CWE-470). CVSS 3.1: 9.8 (CISA ADP); Atlassian: 9.3 (CVSS 4.0). CVE published November 6, 2026; NVD awaiting analysis.
- Atlassian: advisory released November 9, 2026, 22:00 PST; ticket CONFSERVER-104610. Affected: Confluence Data Center 1.x to 9.x with Remote API enabled. Fixed: 9.2.28.
- Rapid7 IOCs (Confluence): 192.238.253[.]176, 5.133.47[.]243, 163.182.68[.]109, 104.13.106[.]166.
- Exploitation: confirmed by Rapid7 MDR (November 13 detection). Not in CISA’s KEV catalog as of its November 13 update. Status: CONFIRMED.
Hunt / verify
- Search Confluence and reverse-proxy access logs for the four Rapid7 addresses, and for requests to
/plugins/servlet/soap-axis1/from outside your network. - Look for processes started by the Confluence Java process, such as shells, curl or wget, and for new or changed files in the Confluence install and home directories.
- If you find a hit, rotate the database account, directory bind account and API tokens Confluence stores, and review recent admin and space-permission changes.
Source: Atlassian advisory; Rapid7
Sources
- Atlassian: CVE-2026-90436 Remote Code Execution in Confluence Data Center
- Rapid7: Detected exploitation of CVE-2026-90436 against Atlassian Confluence Data Center
- Atlassian Jira: CONFSERVER-104610
- NVD: CVE-2026-90436
- Apache announcement: CVE-2026-90436 in Apache Axis 1.x
- N-able: Security update on N-central
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.