CVE-2026-90436 is a remote code execution vulnerability in the Apache Axis library used by Confluence Data Center's XML-RPC and SOAP APIs. Atlassian says a Confluence instance is vulnerable only when its Remote API (XML-RPC & SOAP) setting is enabled. Rapid7 observed exploitation against Confluence Data Center in a customer environment on 13 November 2026.Atlassian rates the issue Critical at CVSS 4.0 9.3 and identifies 9.2.28 as a fixed release. The vendor says Confluence 10.x and Atlassian Cloud are unaffected. The affected setting was disabled by default for new installations starting with Confluence 3.0, but an administrator may have enabled it later.
What it allows
How Does CVE-2026-90436 Enable Code Execution?
Apache's CVE description says Axis 1.x can load and instantiate a class while handling an incoming SOAP fault, before it confirms the class is an expected fault type. A class initializer may run during that process. If a suitable class is present, this can lead to unauthenticated remote code execution.
The fault is parsed before per-service authentication handlers run, according to the Apache-sourced CVE description in NVD. For Confluence, Atlassian says exposure requires the Remote API setting to be enabled. This explains why the same library flaw does not make every Confluence deployment vulnerable.
What Evidence Changes the Response Priority?
Rapid7 MDR says it detected exploitation of CVE-2026-90436 against Confluence Data Center on 13 November 2026. This is a first-hand observation in one customer environment, not a measured count of affected Confluence sites. The CISA KEV catalog snapshot dated 13 November did not list the CVE; that catalog status does not negate Rapid7's observation.
Brandefense Blackhole counted three dark-chat posts mentioning CVE-2026-90436 from 19 August through 17 November 2026. The unit is posts, and discussion does not establish additional attacks. A GitHub search captured for this cycle found one public repository named for the CVE; its listing describes a proof of concept, but its code was not assessed.
Who is affected
Which Confluence Data Center Installations Are Exposed?
Atlassian lists Confluence Data Center 1.x through 9.x as affected when Remote API (XML-RPC & SOAP) is enabled. The setting was off by default for new installations from 3.0 onward, so check the actual setting on each server. Confluence 10.x removed the feature, and Atlassian says its Cloud sites are unaffected.
Atlassian names 9.2.28 as a fixed version and recommends the latest release or a fixed LTS release. Its advisory does not give a separate, comparable fixed threshold for every listed major branch. As an administrator, open General Configuration → System Information and read Confluence Version for the running instance. Compare that build with Atlassian's current advisory, then verify the Remote API state during the patch management process.
How Should Teams Validate Remediation?
Prioritize internet-accessible Confluence instances with the setting enabled, then check internal deployments. Apply the Atlassian update and confirm the running version after service restart or deployment completion. If updating must wait, Atlassian advises turning off the Remote API setting in Further Configuration and confirming it remains clear after saving.
Disabling the setting takes effect without a restart, but Atlassian warns that scripts, automations, or add-ons using the API may stop working. Investigate previously exposed hosts for signs of compromise, using application and host logs plus local security evidence. A vulnerability intelligence platform can support inventory and prioritization, while the vendor advisory remains the source for the fix.
Timeline
- 2026-11-06
NVD published the Apache Axis CVE record.
- 2026-11-09
Atlassian dated its Confluence Data Center advisory and named 9.2.28 as the fixed release.
- 2026-11-13
Rapid7 MDR detected exploitation against Confluence Data Center in a customer environment.
- 2026-11-16
Rapid7 published its first-hand exploitation report.
What to do
-
Inventory Confluence Data Center
Find every Confluence Data Center instance and record its running version, network exposure, owner, and Remote API (XML-RPC & SOAP) setting.
-
Patch exposed installations first
Prioritize reachable instances with Remote API enabled. Update to Atlassian's fixed 9.2.28 release or a current unaffected release, following the vendor advisory for your deployment.
-
Use the vendor mitigation if patching must wait
Disable Remote API (XML-RPC & SOAP) in Further Configuration and save. Confirm the setting remains clear, and test integrations that depend on it.
-
Verify the running version and investigate
After the update, read Confluence Version under General Configuration → System Information on each node. Compare each running build with Atlassian's current advisory and recheck the Remote API setting. Review previously exposed systems for suspicious activity and scope any confirmed compromise.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-90436 in Brandefense Atlas
The Atlas record of CVE-2026-90436: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-90436 affect every Confluence Data Center server?
No. Atlassian says the Remote API (XML-RPC & SOAP) setting must be enabled. Check each server's actual setting and version.
Which Confluence version fixes CVE-2026-90436?
Atlassian names 9.2.28 as a fixed release and says 10.x is unaffected. Confirm the running build against its current advisory.
Has CVE-2026-90436 been exploited against Confluence?
Yes. Rapid7 MDR says it detected exploitation against Confluence Data Center in a customer environment on 13 November 2026.
Can administrators disable the affected feature while patching?
Yes. Atlassian advises clearing Remote API (XML-RPC & SOAP) in Further Configuration. The change takes effect after saving, without a restart, but dependent integrations may stop working.