Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-90436: Unauthenticated Remote Code Execution in Apache Axis 1.x SOAP Fault Processing

Published Nov 6, 2026 · Updated today
Trending this week#19of 427,702 vulnerabilities
Mention activity · 30 days56 mentions · peak 15 in a dayToday
CVSS9.8Critical · v3.1
EPSS1.1%67th percentile
CISA KEVNoNot listed
In the wildReported19 exploitation records in Mallory
Vendor
Apache Software Foundation
IdentifiersCVE-2026-90436CWE-470 · Use of Externally-Controlled Input…

CVE-2026-90436 is an unsafe reflection vulnerability affecting all Apache Axis 1.x versions through 1.4. During inbound SOAP Fault deserialization, Axis loads a class selected through the detail/exceptionName element, triggering its static initializer. If a String data element is present, Axis also invokes the selected class's String constructor before verifying that the resulting object is an AxisFault. A suitable class on the application's classpath can turn this behavior into remote code execution. Fault processing occurs during target-service resolution, before per-service handler chains execute, so service-level authentication handlers do not prevent exploitation. Apache Axis 1.x was end-of-life and unsupported when the vulnerability was assigned.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Unauthenticated attackers can execute arbitrary code with the privileges of the affected Java application, potentially compromising application data, modifying server behavior, and disrupting service availability. Active exploitation has been observed against Confluence Data Center. In N-able N-central, exploitation initially executes commands as the nable service account; the 4EverAble2Shell chain combines this access with a separate local privilege-escalation weakness to obtain root privileges. Root access is not an inherent consequence of CVE-2026-90436 alone.

Mitigation

If you can’t patch tonight, do this now.

Disable affected legacy SOAP interfaces where possible. In Confluence, disable Remote API (XML-RPC & SOAP) under General Configuration and Further Configuration; saving takes effect without a restart but may disrupt integrations. Confirm that requests to the affected SOAP service receive HTTP 403. In N-central, verify that Legacy API is disabled, including on installations running 2026.4 HF2. If an interface cannot immediately be disabled, remove public exposure and restrict access through a VPN or trusted management network. Service-level authentication handlers are ineffective because vulnerable parsing precedes their execution.

Remediation

Patch, then assume compromise.

Migrate from Apache Axis 1.x to a supported SOAP engine, such as Apache Axis 2/Java. Alternatively, build and deploy Axis 1.x with Apache patch commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied; Apache does not expect to publish a fixed Axis 1.x release. For Confluence Data Center, upgrade to fixed version 9.2.28 or an unaffected release; version 10.0 and later removed the affected Remote API feature. For N-central, follow vendor release guidance for 2026.4 HF3, which is intended to permanently remove Legacy API access, and verify update availability. N-central 2026.4 HF2 does not prevent the known exploit chain. Investigate previously exposed systems even after remediation.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
axis-cve-2026-90436-lab-pocStandalone reproduction repository with 12 files: a Python HTTP/SOAP driver, a shell lab builder, a Dockerfile, two Java positive-control gadgets, three evidence logs, a constructor census, README, license and ignore file. Five files contain executable source or build instructions. The census is partially truncated in the supplied material; the README references scan_string_ctors.py, but that script is not included. Repository URL, git reference and archive size were not supplied; empty strings and zero represent unavailable metadata. The claimed vulnerability is unsafe reflection in Axis SOAP fault parsing: exceptionName selects an initializing class load, and a preceding String-typed data element enables constructor invocation before the AxisFault cast. The included gadgets deliberately are not AxisFault subclasses and only write benign markers. Logs report constructor execution against both a known service and a nonexistent service, plus empty-file creation with the stock JDK FileWriter constructor. Stock-install RCE is not demonstrated; the README describes application-specific gadgets as an additional prerequisite. The CVE, affected-version range, exploitation reports and census conclusions are repository claims, not independently verified here. Important implementation defects limit reproducibility. Three Python payloads contain U+200D inside their data closing tags, making the XML malformed. Content-Length is calculated from Unicode character count rather than encoded byte count, further corrupting framing for those payloads. HTTP error responses alone do not establish exploitation, and the driver does not inspect markers automatically. Its static-only probe reuses poc.Gadget after the constructor probe, so it cannot independently demonstrate a fresh static initialization; Gadget2 is not invoked by the driver. Supplied evidence logs therefore do not establish that the exact displayed driver produced the recorded successful constructor results. The build downloads official Apache archives without explicit checksum verification and installs the custom gadget JAR into Axis. Despite documentation claiming loopback-only binding, Docker is invoked with -p 18080:8080 and no host IP, normally exposing the intentionally vulnerable lab on all host interfaces. No reverse shell, credential theft, exfiltration destination or concealed destructive command is present. The documentation's proposed mitigation is non-initializing class loading plus assignability checks; the vulnerable Axis sources and patch are not included.dinosn · Disclosed Nov 17, 2026 · python · sh · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationAxisapplication
FAQ

Frequently asked questions

Is CVE-2026-90436 exploited in the wild?
Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-90436?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-90436, the earliest disclosed Nov 17, 2026.
Is there a patch for CVE-2026-90436?
Migrate from Apache Axis 1.x to a supported SOAP engine, such as Apache Axis 2/Java. Alternatively, build and deploy Axis 1.x with Apache patch commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied; Apache does not expect to publish a fixed Axis 1.x release.
What products are affected by CVE-2026-90436?
Apache Software Foundation Axis.
How severe is CVE-2026-90436?
CVE-2026-90436 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.1% (67th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

56 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cryptika blogNews · Nov 17, 2026Hackers Actively Exploiting Atlassian Confluence RCE Vulnerability, 1.2M Instances Exposed to the Internet | Cryptika CybersecurityA critical pre-authentication remote code execution vulnerability in Apache Axis 1.x SOAP fault processing, rated CVSS v4.0 9.3. Axis loads an attacker-specified Java class before validating its expected error type. Confluence Data Center 1.x through 9.x is affected when the Remote API is enabled and a suitable class is available. Rapid7 detected exploitation on November 13, 2026. The reported 1,212,568 internet-facing web properties are not confirmed vulnerable installations. Confluence 10.0 removed the feature, and Atlassian Cloud is unaffected.Read more ↗cyber security newsNews · Nov 17, 2026Hackers Actively Exploiting Atlassian Confluence RCE Vulnerability, 1.2M Instances Exposed to InternetA critical Apache Axis 1.x flaw enabling unauthenticated remote code execution through specially crafted SOAP fault messages. Axis loads an attacker-specified Java class before validating its type and before service-level authentication. Confluence Data Center versions 1.x through 9.x are affected when the Remote API is enabled and a suitable class is available. Rapid7 detected exploitation on November 13, 2026. The reported 1,212,568 exposed web properties are not confirmed vulnerable installations. Confluence Data Center 9.2.28 fixes the issue; version 10.0 removed the affected feature. Disabling the Remote API provides temporary protection.Read more ↗rapid7 blogNews · Nov 16, 2026Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also ExploitedA critical unsafe reflection vulnerability in Apache Axis 1.x through 1.4 permits unauthenticated remote code execution and has a reported CVSS score of 9.8. Exploitation is reported against Atlassian Confluence Data Center with Remote API (XML-RPC & SOAP) enabled and N-able N-central with Legacy API enabled; both require non-default configurations. A public proof-of-concept targeting N-central was published on November 12, 2026. Confluence 9.2.28 fixes the issue, while 10.x removes the affected feature. Axis 1.x is end-of-life, but a patch is available to apply to a build. N-central mitigations include disabling Legacy API, with permanent removal through version 2026.4 HF3; hosted upgrades are reported complete, while on-premises availability is being finalized.Read more ↗sh3llc0d3 blogNews · Nov 16, 20264EverAble2Shell Bypasses N-central Hotfix | ShellcodeAn Apache Axis 1.x SOAP service-handling vulnerability rated CVSS 9.8. The article identifies it as the entry point in the actively exploited 4EverAble2Shell chain against N-central appliances with the Legacy API enabled. Disabling that API and restricting network exposure are recommended mitigations; Hotfix 2 does not block the chain.Read more ↗
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware8Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity34Community discussion across Reddit, Mastodon, and other social sources.