Confluence CVE-2026-90436 Exploited via Apache Axis RCE
Security

Confluence CVE-2026-90436 Exploited via Apache Axis RCE

Confluence CVE-2026-90436 lets attackers run code through the legacy Remote API. Rapid7 saw exploitation Nov 13. Upgrade to 9.2.28 or disable the API.

confluenceapache axisremote code executionatlassianactively exploited

Confluence CVE-2026-90436 is an unauthenticated remote code execution flaw in the Apache Axis 1.x library that Confluence Data Center uses for its XML-RPC and SOAP APIs. Rapid7 detected exploitation against a customer's Confluence server on November 13, 2026. Only instances with the "Remote API (XML-RPC & SOAP)" setting enabled are exposed. Upgrade to Confluence Data Center 9.2.28 or a 10.x release, or switch the Remote API off today, then check exposed servers for signs of compromise.

What happened

The Apache Software Foundation disclosed CVE-2026-90436 on November 6, 2026. The bug sits in Apache Axis 1.x, an old Java SOAP engine that the Axis project no longer supports. When Axis parses an inbound SOAP fault, it reads a class name from the message and loads that class before checking that it is the error type it expects. Loading a class runs its static initializer, and with a suitable class on the application's classpath that leads to code execution.

Atlassian published its advisory on November 9 and rated the issue Critical, CVSS 4.0 base score 9.3. The CISA ADP enrichment on the CVE record scores it 9.8 under CVSS 3.1. Atlassian tracks it as CONFSERVER-104610.

A public lab proof of concept for the Axis flaw appeared on November 10, according to Censys. It creates or truncates files and does not show code execution against Confluence. On November 13, Rapid7's managed detection team saw exploitation against Confluence Data Center in a customer environment. Rapid7 has not described what the attacker did after getting in.

The same Axis flaw is the first step in a separate public exploit chain against N-able N-central, published November 12. N-able reported in-the-wild exploitation of N-central on November 13 and shipped N-central 2026.4 HF3 (2026.4.1.39) on November 16, which disables the Legacy API.

Who is affected by Confluence CVE-2026-90436

Per Atlassian's advisory:

  • Affected: Confluence Data Center 1.x through 9.x, but only when "Remote API (XML-RPC & SOAP)" is enabled.
  • Fixed: Confluence Data Center 9.2.28 is the only fixed build Atlassian lists. Confluence 10.0 removed the Remote API feature entirely, so 10.x releases are not affected.
  • Not affected: Atlassian Cloud sites on atlassian.net or jira.com. No action is required there.

The Remote API has been off by default for new installations since Confluence 3.0. The risk sits with older instances that were upgraded in place with the setting carried forward, and with teams that turned it on for a script, integration or add-on. Atlassian notes that it no longer releases binary patches, so the fix is an upgrade.

Censys counted 1,212,568 internet-facing Confluence web properties on November 16. That figure counts every hostname and port where Confluence answers. It does not check versions or whether the Remote API is on, so it is an upper bound on exposure, not a count of vulnerable servers.

Debian's own axis package is listed as vulnerable with no fix, and the Axis project does not plan a 1.x release. Any in-house Java application that still embeds Axis 1.x carries the same flaw and needs its own review.

Technical analysis

The CVE record classifies the bug as CWE-470, use of externally controlled input to select classes or code. We explain that weakness class in what unsafe reflection is and why it leads to code execution.

Two details make this one serious. First, Axis parses the SOAP fault while it is still working out which service the request targets, before any per-service handler chain runs. Authentication handlers attached to a service never get a chance to reject the request, which is why it is unauthenticated. Second, exploitation depends on which classes are already on the classpath. Confluence ships a large set of Java libraries, and the exploitation Rapid7 observed shows that attackers found a workable path.

Atlassian says a successful attacker can run arbitrary commands as the Confluence operating system account. That puts application data, stored secrets and files on the server within reach, and gives the attacker a foothold inside the network.

Apache published a patch commit (41f3b4e8) for anyone building Axis 1.x from source, and recommends moving to Apache Axis 2 instead.

What to do now

  1. Find every Confluence Data Center instance, including internal and test servers, and record its version.
  2. Check the Remote API setting. In Confluence, go to General Configuration, then Further Configuration. If "Remote API (XML-RPC & SOAP)" is ticked, the instance is exposed. Our step by step guide covers how to disable the Confluence Remote API and confirm it is off.
  3. Upgrade exposed instances to 9.2.28 or the latest release. Rapid7 advises doing this on an emergency basis outside normal patch cycles.
  4. If you cannot upgrade today, clear the Remote API checkbox and save. Atlassian says the change takes effect without a restart but may break scripts, automations and add-ons that depend on the API. Atlassian calls this an interim mitigation, not a fix.
  5. Verify the mitigation. Browse to <base_url>/plugins/servlet/soap-axis1/confluenceservice-v2. Atlassian says a mitigated instance returns HTTP 403 Forbidden. A response that mentions "confluenceservice-v2" or "AXIS service" means the API is still reachable.
  6. Hunt for compromise on any instance that had the Remote API on while reachable. Rapid7 published these Confluence-related IP addresses:
192.238.253[.]176
5.133.47[.]243
163.182.68[.]109
104.13.106[.]166

Rapid7 cautions that the absence of these addresses in your logs does not prove a server is clean. Atlassian also states it cannot confirm whether customer instances were affected, so the investigation is on you. Look for new or unexpected processes started by the Confluence service account, outbound connections from the Confluence host, and changes to files in the installation directory since November 6.

If you run N-able N-central on premises, confirm the Legacy API is disabled and upgrade to 2026.4 HF3. We covered an earlier N-central emergency in September, and this is a separate issue.

Why this keeps happening

Confluence's Remote API has been off by default for new installs since version 3.0, and Atlassian removed it in 10.0. Instances still running it today usually do so because nobody went back to check. That pattern, an old API kept alive for one integration, is the subject of why you should switch off unused legacy APIs. It is also the second Atlassian Data Center flaw tied to a shared component in six weeks, after the CVE-2026-21589 file read bug in October.

What to watch next

  • CISA KEV. CVE-2026-90436 was not in the KEV catalog as of the November 13 release. A listing would set a federal deadline and usually triggers wider scanning.
  • Post-exploitation detail. Rapid7 has not said what the attacker did after access. Ransomware groups have used earlier Confluence flaws, so watch for attribution.
  • More fixed builds. Atlassian lists only 9.2.28. Check the advisory for additional LTS fixes before planning upgrades on other branches.
  • Other products embedding Axis 1.x. N-central and Confluence are the first two confirmed. Expect more vendor advisories.

Sources