CVE Tools

CVE-2026-90436

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

No known exploitation. EPSS puts it in the 67th percentile. No fix published yet.

Check it yourself

OpenVAS · 1 check

e.g. OID 1.3.6.1.4.1.25623.1.0.148543

Run the check

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • Apache Software Foundation Apache Axis 1.xAffected: ≤ 1.4Upgrade to: after 1.4Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Ask your IT team or vendor whether any system uses Apache Axis 1.x (sometimes bundled inside older Java web applications) to send or receive SOAP web service messages.
  2. If found, treat it as high risk since this software is no longer supported and has no official fixed version.
  3. Plan to migrate the affected application to a maintained SOAP engine such as Apache Axis2/Java.
  4. If migration isn't possible right away, have a developer apply the patch from Apache's commit (41f3b4e8) to your Axis 1.x build as a stop-gap.
  5. Restrict network access to the service so it isn't reachable from the open internet while you migrate.

What it is

From the CVE record

** 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.

In plain language

Written by AI from the record

If your business still runs the old, discontinued Apache Axis 1.x software to handle web service messages, an attacker could take over the server without logging in — this needs attention, but there's no sign anyone is exploiting it yet.

Apache Axis 1.x (EOL) deserializes the exceptionName/data fields of an inbound SOAP Fault before any authentication handler runs, causing unauthenticated remote class loading and, with a suitable classpath class, instantiation via its String constructor — leading to remote code execution.

If you're affected

  • Full server takeover
  • Customer data exposure
  • Operational disruption
  • Ransomware risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS67th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.1% chance of exploitation activity in the next 30 days, which ranks it in the 67th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained, driven by wide press coverage.

Lifecycle

8 events over 146 days, from the signal feeds we watch.

  1. Record updated
  2. Record updated
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated
  5. OpenVAS check added

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache Axis 1.x (EOL), not every advisory.