Skip to content

Confluence Data Center is under active attack via an old Apache Axis bug

CVE-2026-90436 lets an unauthenticated attacker run code on self-hosted Confluence through its legacy SOAP API. Rapid7 confirms exploitation started on 13 November.

Source: Atlassian

Atlassian disclosed CVE-2026-90436 on 9 November: a critical, unauthenticated remote code execution bug in Confluence Data Center, carrying a CVSS score of 9.3. The flaw actually sits in Apache Axis 1.x, a SOAP library Confluence bundles for its legacy Remote API. Sending a crafted SOAP fault lets an attacker trigger unsafe deserialisation and run arbitrary code, no login required.

It hits Confluence Data Center 1.x through 9.x, but only where the “Remote API (XML-RPC & SOAP)” setting is switched on; Confluence 10.x and Confluence Cloud removed that interface and are not affected. Atlassian has shipped fixed builds, including 9.2.28, and the advisory lists disabling the Remote API setting as an immediate stopgap for anyone who cannot upgrade yet. Apache itself has no fixed Axis 1.x release coming, since the library is end of life. On 16 November, Rapid7 reported its MDR team had detected real-world exploitation against a Confluence Data Center customer starting 13 November, and separately linked an N-able N-central attack to the same flaw.

Why it matters: this is a four-day-old disclosure already being exploited, against a tool a lot of engineering teams self-host for documentation and wikis. If you run Confluence Data Center with the Remote API switched on, patch or disable that setting now rather than waiting for a quiet maintenance window.

The caveat: Atlassian’s fix updates Confluence’s bundled Axis, not Axis itself. Anything else in your stack still running Axis 1.x against untrusted SOAP input has the same exposure and needs its own check.

Share

Related reading

More from The Wire

All briefs