Confluence Data Center CVE-2026-90436 Now Exploited: Unpatchable Apache Axis 1.x SOAP Flaw Gives Unauthenticated RCE When the Remote API Is On — Update to 9.2.28

Cyber · 2026-11-17 · By H.A

Confluence Data Center CVE-2026-90436 Now Exploited: Unpatchable Apache Axis 1.x SOAP Flaw Gives Unauthenticated RCE When the Remote API Is On — Update to 9.2.28

Attackers began exploiting CVE-2026-90436 in Confluence Data Center on 13 November, a week after Apache disclosed an unauthenticated SOAP-fault class-loading flaw in end-of-life Axis 1.x that it will not fix, so admins should update to 9.2.28 or disable the Remote API now.

A critical flaw in Apache Axis 1.x, an old SOAP library that went end-of-life years ago but still ships inside commercial software, is now being exploited against Atlassian Confluence Data Center. The bug, tracked as CVE-2026-90436, lets an unauthenticated attacker make the server load and instantiate Java classes of their choosing. Atlassian rates it critical (CVSS v4.0 9.3), and the CISA-supplied CVSS v3.1 score in the NVD record is 9.8.

Security researchers running a managed detection service say they saw the flaw exploited against a customer's Confluence Data Center server on 13 November. That makes Confluence the second product, after N-able N-central, where the same Axis bug has been used in real intrusions within a week of disclosure.

What Happened

The timeline has moved fast:

When Atlassian published, its advisory said nothing about exploitation, and as of 17 November the CVE was not in CISA's Known Exploited Vulnerabilities (KEV) catalog. CISA's own SSVC assessment in the NVD record, dated 10 November, still lists exploitation as "none" but marks the flaw as "automatable" with "total" technical impact. Don't treat the missing KEV entry as a sign that the risk is low.

Technical Details

The bug is in how Axis 1.x handles SOAP fault messages. A fault can name the exception that caused it in an <exceptionName> element. Axis takes that string as a Java class name and loads it, which runs the class's static initialiser. If a string <data> element is also present, Axis calls the class's single-string constructor, and only then checks whether the object is an AxisFault. By that point the attacker-chosen code has already run, and the resulting cast error is quietly swallowed.

Three things make this worse than an ordinary parsing bug:

The upstream fix (commit 41f3b4e8) loads the class without initialising it, rejects anything that is not an AxisFault subclass before construction, and gates the reflective constructor call on that check.

Who Is Affected

Patch Status

Atlassian's fixed Confluence Data Center release is 9.2.28. The company recommends moving to the latest version or a fixed Long Term Support release, and says critical fixes are backported to maintenance releases but no standalone binary patches will be issued. Confluence 10.x is unaffected.

For Axis itself, no official fixed release exists or is planned. Teams maintaining their own Axis 1.x builds can apply the upstream commit, but Apache's recommended path is to migrate to another SOAP stack such as Axis2/Java.

What To Do Now

curl -s -o /dev/null -w '%{http_code}\n' https://confluence.example.internal/plugins/servlet/soap-axis1/confluenceservice-v2

Why It Matters

Confluence has a long history as a ransomware entry point, and attackers move fast on its bugs. This case adds a supply-chain twist. The vulnerable code sits in a library whose maintainers have formally stopped releasing fixes, so protection depends on each downstream vendor noticing, patching and telling customers. Atlassian's answer was to delete the feature in version 10. N-able's is to remove Legacy API access in a hotfix. Everyone else that still ships Axis 1.x, including in-house applications, is on their own.

Exploitation also came fast. The CVE went public on 6 November, a working lab proof of concept followed four days later, and real attacks reached two separate product families within a week, before CISA's catalog listed it. For defenders, this is another sign that end-of-life components in the software bill of materials can't wait for the next maintenance window. Deprecated, off-by-default features that stay enabled on old installs are exactly what attackers look for first.

Sources

REEF SENTINEL