SardinhaNews

CVE-2026-90436

CriticalBDU · public exploit

Published: 11/06/2026 · Modified: 11/12/2026

CVSS 3.1ⓘ9.8
EPSSⓘ1.1%
VPR (Tenable)9.2

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.

Exploitation

Requires: network access · Does not require: authentication, user interaction, special target conditions

How it is exploited

Exploitation method

  • The attacker sends a SOAP request to the Apache Axis 1.x service, without authentication.
  • The message contains a SOAP <Fault> element with <detail><exceptionName> pointing to a class present on the application's classpath.
  • Axis loads the named class; if a String <data> element is also present, it instantiates the class through its String constructor before checking that it is an AxisFault.
  • Loading alone runs the class's static initializer, and instantiation through the String constructor is also triggered.
  • With a suitable class on the classpath, this leads to remote code execution; the fault is parsed before any per-service handler chain runs, so authentication configured on a service does not protect against it.

Am I affected? (applicability)

  • Apache Axis 1.x is in use, in any version through 1.4.
  • The Axis SOAP service is exposed to the network and reachable by the attacker.
  • The application's classpath contains a suitable class that, when loaded or instantiated through a String constructor, allows code execution.
  • Authentication handlers are configured on the service, but they do not protect because the fault is parsed before the handler chain runs.

Does not require: authentication, user interaction, special target conditions.

Mitigation and detection

✓ Fix available in version 41f3b4e8d04e310ca81f86b92630ab2c11d608bd

  • Migrate to another SOAP engine, such as Apache Axis 2/Java, or apply the vendor fix (patch from commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd) to an Axis build.
  • Restrict network access to the Axis SOAP service to trusted clients only.
  • Review the application's classpath to remove classes that could be abused through loading or instantiation via a String constructor.

Impact if exploited

Unauthenticated remote code execution on the server hosting Apache Axis 1.x, with loss of confidentiality, integrity, and availability of the system.

Confidentiality: highIntegrity: highAvailability: high

Community reports (unverified): PoC 1

References and technical detail

The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.

Exploitation probability (EPSS) over time

11/08/202611/12/2026

Weakness type (CWE)

In the news

Timeline on SardinhaNews

References