CVE-2026-90436
Apache Axis 1.x SOAP fault deserialization allows unauthenticated remote code execution (CVE-2026-90436)
Apache Axis 1.x through 1.4 has an unauthenticated SOAP fault deserialization flaw that can lead to remote code execution. CISA and ENISA list it as actively exploited. No Axis 1.x fix is planned; migrate to another SOAP engine or apply commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd.
What happened
An unauthenticated attacker who can reach an Apache Axis 1.x SOAP endpoint can submit a crafted SOAP fault whose <detail><exceptionName> element names a class on the server. Axis loads that class before checking that it is an AxisFault. Loading alone runs the class's static initializer; if the fault also includes a String <data> element, Axis calls the class's String constructor. With a suitable class on the application classpath, this leads to remote code execution.
The fault is parsed while Axis resolves the target service, before any per-service handler chain runs, so authentication handlers configured on a service do not stop it. The CVSS 3.1 score is 9.8 critical: network reachable, low complexity, no privileges and no user interaction required.
CISA added the CVE to its Known Exploited Vulnerabilities catalog on 18 November 2026, CISA's SSVC assessment records active exploitation, and ENISA's EUVD records exploitation since 18 November 2026. Apache states that Axis 1.x is end-of-life and does not expect to create a fixing release.
Who is affected
All Apache Axis 1.x versions up to and including 1.4 are affected. Axis 1.x is a Java SOAP engine, so affected deployments may be standalone SOAP services or Java applications that embed the engine. Typical deployments expose SOAP web services on an application server; any Axis 1.x SOAP endpoint reachable from an untrusted network should be treated as exposed.
What to do now
- Inventory Java applications and shared libraries that include Axis 1.x, including transitive dependencies. Every version through 1.4 is affected.
- Restrict network access to any Axis 1.x SOAP endpoint, or take it offline, while remediation is planned.
- Choose a remediation path: migrate to a supported SOAP engine such as Apache Axis 2/Java, or rebuild Axis 1.x with commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. There is no fixed Axis 1.x release and none is planned.
- Because CISA KEV, CISA SSVC and ENISA EUVD list the vulnerability as actively exploited, treat unexplained activity on affected systems as a possible incident and invoke the incident response process. CISA has not set a remediation due date in the KEV entry.
How to detect it
Begin with exposure discovery: identify Axis 1.x deployments and any SOAP endpoints reachable from untrusted networks. In web service or application logs, look for inbound SOAP faults carrying a <detail><exceptionName> element, and review unexpected class-loading failures or static initializer activity linked to SOAP requests.
Beyond the patch
Active exploitation makes this a detection-and-response problem as much as a remediation one. Managed Detection & Response (MDR) is the first line for watching for activity on affected systems, and Virtual CISO Services can help find and close internet-exposed SOAP endpoints before they are targeted.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| Apache Axis 1.x (EOL) | – ≤ 1.4 | 41f3b4e8d04e310ca81f86b92630ab2c11d608bd |
| Apache Axis 1.x (EOL) | aac718c6035435d96b39d6aebb9c078a13af7cc8 – < 41f3b4e8d04e310ca81f86b92630ab2c11d608bd | 41f3b4e8d04e310ca81f86b92630ab2c11d608bd |