CISA has added CVE-2026-90436, a critical unauthenticated code execution flaw in end-of-life Apache Axis 1.x, to its Known Exploited Vulnerabilities catalog, which confirms active exploitation, and Apache will not release a fixed 1.x version.
What Is It
CVE-2026-90436 is an unsafe reflection weakness (CWE-470) in how Apache Axis 1.x deserializes inbound SOAP fault messages. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the class it names. If a String <data> element is also present, Axis creates the class through its String constructor before checking whether the class is an AxisFault. Just loading the class runs its static initializer. If a suitable class is on the application's classpath, this leads to remote code execution.
Axis parses the fault while it is still working out which service the request is for. This happens before any per-service handler chain runs, so authentication handlers configured on a service do not block the attack.
Why It Matters
- Confirmed exploitation: CISA added this CVE to the KEV catalog on 2026-11-18, which confirms it is being exploited in the wild.
- Severity: CVSS 3.1 base score 9.8 (Critical), vector
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. It needs no authentication and no user interaction. - Federal deadline: The KEV due date is 2026-11-21.
- Forensic triage: KEV flags this entry for forensic triage under CISA's BOD 26-04 implementation guidance.
- Ransomware: KEV lists known ransomware campaign use as "Unknown."
- Wide reach: KEV notes that the flaw could affect an open-source component or library that other products use.
What's Vulnerable
- All Apache Axis 1.x versions through 1.4 (Maven packages
axis:axisandorg.apache.axis:axis) - Axis 1 source builds that predate commit
41f3b4e8d04e310ca81f86b92630ab2c11d608bd
The CVE was tagged "unsupported when assigned" because Axis 1.x is end-of-life.
Patch Status
Apache does not plan to ship a fixed Axis 1.x release. It recommends migrating to a different SOAP engine, such as Apache Axis2/Java. The alternative is to run a build of Axis with the upstream patch commit applied.
CISA's required action is to apply mitigations according to vendor instructions and follow BOD 26-04 and its Forensics Triage Requirements. If no mitigations are available, stop using the product. CISA advises users to transition away from the EoL product, and asset owners should check each deployment's internet exposure.