Apache Axis 1.x (EOL): unauthenticated remote class instantiation via SOAP fault exceptionName
Get instant alerts when new vulnerabilities affect Apache Axis 1.x (EOL) - before attackers find them.
CISA Known Exploited Vulnerabilities (KEV) Catalog
EPSS (Exploit Prediction Scoring System) estimates a 3.8% chance this CVE is exploited in the wild within the next 30 days — higher than 90% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.
Apache Axis contains an unsafe reflection vulnerability that could allow an unauthenticated remote attacker to execute arbitrary code via a crafted SOAP fault message that causes Axis to load and instantiate an attacker-specified class when a suitable class is available on the application classpath. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
** 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.
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Generated by AI (claude-fable-5.1) and published by VulnTracker. It is not reviewed by a person, so check the vendor advisory before you act on it.
Migrate every application off Apache Axis 1.x (no fixed upstream release will be made) or run a build with the upstream patch applied, and on openSUSE Tumbleweed update the axis package to 1.4-311.1 or later; this flaw is exploited in the wild with a KEV due date of 2026-11-21.
A fix is recorded
Guidance updated 2026-11-20
Sign in free to see the steps, fixed versions and workarounds.
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
Get alerted
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
This product uses data from the NVD API but is not endorsed or certified by the NVD. CVE records are from the CVE Program (CVE.org).