Skip to content
Sign in
CVE-2026-904369.8Critical

CVE-2026-90436: Apache Axis 1.x (EOL): unauthenticated remote class instantiation via SOAP fault exceptionName

Apache Software Foundation · Apache Axis 1.x (EOL)

No distribution fix yet for Debian 12/13 · Affected: Apache Software Foundation Apache Axis 1.x (EOL) · Exploitation: public proof of concept (unverified)

ExploitationProof of concept public

Not in CISA KEV as of catalogue 2026.11.10 (10 Nov)

  1. In CISA KEV: not seen
  2. Exploited (reported): not seen
  3. Scanning observed: not seen
  4. Proof of concept public1 public GitHub repository (unverified), listed by PoC-in-GitHub10 Nov
  5. Not established: not seen
0.6%probability of exploitation in the next 30 days
47th percentile
050100

Higher than 47% of scored CVEs

9.8CriticalCVSS
LowCrit.

DescriptionNVD

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.

Fix status by distribution

From each distribution’s security tracker. Distributions we did not check are not listed.

What changed

Debian status tracked since 12 Nov 2026. Ubuntu status tracked since 12 Nov 2026.

  1. Debian’s tracker lists Debian 12 as affected, with no fix released Debian
  2. Debian’s tracker lists Debian 13 as affected, with no fix released Debian
  3. Ubuntu’s tracker lists Ubuntu 16.04 as under investigation Ubuntu
  4. Ubuntu’s tracker lists Ubuntu 18.04 as under investigation Ubuntu
  5. Ubuntu’s tracker lists Ubuntu 20.04 as under investigation Ubuntu
  6. Ubuntu’s tracker lists Ubuntu 22.04 as under investigation Ubuntu
  7. Ubuntu’s tracker lists Ubuntu 24.04 as under investigation Ubuntu
  8. Ubuntu’s tracker lists Ubuntu 26.04 as under investigation Ubuntu
  9. Ubuntu’s tracker lists Ubuntu stonking as under investigation Ubuntu
  10. PoC-in-GitHub lists 1 public GitHub repository (unverified) PoC-in-GitHub

Coverage1 article · 1 outlet

First in our coverage: The Hacker News, 12 Nov.

New articles also arrive in the RSS feed.

References

Updated AboutDevelopersSign in