Summary
generated automatically from NVD dataApache Axis 1.x, through version 1.4 and now end-of-life, deserializes inbound SOAP faults unsafely: a fault with a detail exceptionName element makes Axis load the named class and instantiate it via its String constructor before checking it is an AxisFault. An unauthenticated remote attacker can thereby run static initializers and, with a suitable class on the classpath, achieve remote code execution, bypassing service authentication handlers. It is rated CRITICAL (CVSS 9.8) and listed in the CISA KEV catalog; the project recommends migrating to Axis 2/Java or applying a published patch, and expects no Axis 1.x fix release.
NVD description
** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class and, if a String <data> element is also present, instantiates it through its String constructor before checking that it is an AxisFault. Loading alone runs the class's static initializer. With a suitable class on the application's classpath this leads to remote code execution. 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 do not protect against it. This affects all Apache Axis 1.x versions through 1.4. As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.
⚠️ Actively exploited — CISA KEV
This CVE was added to CISA's Known Exploited Vulnerabilities catalog on 2026-11-18. It is confirmed exploited in the wild and must be patched as a priority.
Remediation deadline (US federal agencies): 2026-11-21
EPSS · FIRST.org
1.8%probability of exploitation in the next 30 days
Higher than 79% of scored CVEs
EPSS (Exploit Prediction Scoring System) estimates, from observed exploitation activity, how likely a CVE is to be exploited in the next 30 days. It complements CVSS, which measures severity, not likelihood. Score of 2026-11-20, recomputed daily by FIRST.org.
In-depth analysis on cveo.tech
This CVE is covered in an article: context, affected versions and published fixes.
CVSS v3.1 Score
Information
- Published
- 6 nov. 2026
- Updated
- 19 nov. 2026
- Status
- Analyzed
- Source
- security@apache.org
Affected products
Bounds published by NVD: "< 8.4.27" means 8.4.27 is no longer vulnerable. The fixed release to install is in the vendor advisory.
Weaknesses (CWE)
References (4)
- https://lists.apache.org/thread.html/8slf0j9gz35z56t0glt5h0ncwlbn4bdzMailing ListVendor Advisory
- http://www.openwall.com/lists/oss-security/2026/11/06/12Mailing ListThird Party Advisory
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-90436US Government Resource
Similar CVEs
Other vulnerabilities of type CWE-470
Know which CVEs hit the versions you run.
Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.