One EOL SOAP Engine, Two Vendors, Zero-Days: CVE-2026-90436 and the Persistent Attack Surface of Legacy Libraries

TL;DR: CVE-2026-90436 is a CVSS 9.8 unauthenticated RCE in Apache Axis 1.x, an EOL SOAP engine. It’s actively exploited against Confluence Data Center and N-able N-central. CISA KEV due date is 2026-11-21. Apache won’t publish a fixed Axis 1.x release. The lesson isn’t about one CVE — it’s about how legacy libraries become persistent attack surfaces across unrelated products.

The Vulnerability

On November 6, 2026, the Apache Software Foundation disclosed CVE-2026-90436, a critical unsafe reflection vulnerability (CWE-470) in Axis 1.x through 1.4.

Axis 1.x deserializes inbound SOAP fault messages by loading the class named in the <detail><exceptionName> element, then instantiating it via its String constructor before checking that it’s an AxisFault. Loading the class triggers its static initializer. With a suitable class on the application’s classpath, that’s remote code execution.

Key detail: the fault is parsed while the engine resolves the target service, before any per-service handler chain runs. So authentication handlers configured on a service don’t protect against it. Unauthenticated.

CISA scored it 9.8 (CVSS 3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Two Vendors, Same Library, Different Symptoms

Atlassian Confluence Data Center

Atlassian’s advisory (published November 9, 2026) lists Confluence Data Center 1.x through 9.x as affected. Exploitation requires the “Remote API (XML-RPC & SOAP)” setting to be enabled — off by default since Confluence 3.0, fully removed in 10.0.

Rapid7 MDR detected exploitation on November 13 in a customer environment. The attacker sent unauthenticated POST requests to /plugins/servlet/soap-axis1/confluenceservice-v2, got HTTP 500 responses, but the Confluence Java process was launching Bash and curl as the service account within seconds. Hundreds of hex-encoded shell commands followed, fetched from Pinggy and Cloudflare Tunnel domains, wrapped in labeled delimiters with sequential task IDs — AI-assisted automation.

Atlassian fixed the issue in Confluence Data Center 9.2.28. Confluence 10.x is unaffected (feature removed). Atlassian Cloud is unaffected.

N-able N-central

Some N-central versions bundle the affected Axis library. Exploitation requires the “Legacy API” setting enabled — off by default.

Sean Bales published the 4EverAble2Shell PoC on November 12, chaining CVE-2026-90436 (Axis RCE as the nable service account) with a separate N-central privilege escalation (abusing setLDFileOwner helper + symlink to make a root-owned script writable). Hours after PoC release, threat actors were deploying XMRig Monero miners on at least 21 production N-central servers — 19 of them on 2026.4.1.26, the latest hotfix released November 10.

N-able released HF3 (2026.4.1.39) on November 16, which permanently disables the Legacy API. Huntback reported that the attackers’ naming convention (nc_<IP>) in their mining pool made compromise detection straightforward.

The CISA KEV Angle

CISA added CVE-2026-90436 to the KEV catalog on November 18, with a due date of November 21 — three days. That’s fast for CISA; it signals active exploitation with confirmed impact.

For agencies following BOD 26-04, this means applying vendor mitigations or patching by tomorrow.

The Bigger Pattern: EOL Libraries as Persistent Attack Surfaces

Apache Axis 1.x reached end of life years ago. Apache expects to publish no fixed Axis 1.x release. The recommendation is to migrate to Axis 2 or apply the patch commit to a self-built Axis 1.x.

But the Axis 1.x code is embedded in dozens of products: Confluence, N-central, and likely others that haven’t been discovered yet. When the upstream library goes EOL without a fixed release, every downstream vendor becomes its own security team for that component.

This isn’t the first time this pattern has played out:

  • Log4Shell (CVE-2021-44228): EOL-era logging library, exploited everywhere that used it.
  • Apache Axis 1.x today: EOL SOAP engine, exploited wherever it’s still wired up.
  • Older examples: Struts 1.x (2013 EOL, still found in wild), Commons FileUpload, Jython.

The pattern: legacy libraries don’t die. They get copied, embedded, forgotten, and then someone writes a PoC that hits all of them at once.

What to Do Now

Confluence Data Center:

  • Upgrade to 9.2.28 or any 10.x release.
  • Or disable “Remote API (XML-RPC & SOAP)” in General Configuration (no restart required).
  • Check access logs for POSTs to /plugins/servlet/soap-axis1/confluenceservice-v2 returning 500.

N-able N-central:

  • Upgrade to 2026.4 HF3 (2026.4.1.39).
  • Or confirm Legacy API is disabled (even on HF2).
  • Check for IOCs: 157.20.241.16, 139.99.69.109, 79.76.51.56.

Other Axis 1.x users:

  • Identify every product bundling Axis 1.x ≤ 1.4.
  • Disable or migrate the SOAP endpoint.
  • Apache’s patch commit: 41f3b4e8d04e310ca81f86b92630ab2c11d608bd.

General:

  • Metasploit module released November 17 — if your scanner supports it, run it against your SOAP endpoints.
  • The EPSS score is 1.1% — low because it requires non-default configuration, but actively exploited in the wild means the real exploitation probability is higher than the model predicts.

Why This Matters for Vulnerability Management

CVE-2026-90436 is a textbook example of why EPSS matters more than CVSS for prioritization:

  • CVSS 9.8: sounds like patch everything immediately.
  • EPSS 1.1%: the model thinks it’s unlikely to be exploited (because most Axis 1.x deployments don’t have the right setting enabled).
  • But: among the exploited instances, impact is RCE. And exploitation is actively detected.

The right move: check your inventory for Axis 1.x → check the configuration → patch or mitigate based on exposure, not the base score.

And the longer-term lesson: audit your legacy dependencies. Not just the CVEs they have today, but the ones they will have when the next PoC writer finds them.


Sources: Apache Software Foundation (Nov 6), Atlassian (Nov 9), Rapid7 MDR report (Nov 13), N-able advisory and HF3 release (Nov 12-16), CISA KEV (Nov 18), BleepingComputer/Huntback exploitation reports (Nov 12).