Apache Axis 1.x RCE flaw exploited in the wild (CVE-2026-90436)

Apache Axis 1.x RCE flaw exploited in the wild (CVE-2026-90436)

At a glance

SeverityCRITICAL
CVSSCVE-2026-90436: 9.8
EPSS (30-day exploit probability)CVE-2026-90436: 1.8%
In CISA KEV (exploited)Yes, due 2026-11-21
VendorApache
CVE IDsCVE-2026-90436

Primary-source details

Apache Axis 1.x contains an unsafe reflection flaw, tracked as CVE-2026-90436, that lets an unauthenticated attacker run code remotely, and CISA has added it to its Known Exploited Vulnerabilities catalog. This Apache Axis vulnerability affects every 1.x release through 1.4, no fixed release is planned, and the CISA due date for federal agencies is 21 November 2026. CISA’s KEV entry was added on 18 November 2026.

What happened

When Axis receives a SOAP fault that carries a detail element with an exceptionName, it loads the class named there. If a String data element is also present, Axis creates an instance through that class’s String constructor, and only afterwards checks that it is really an AxisFault.

Merely loading a class runs its static initializer. If a suitable class is on the application’s classpath, the result is remote code execution, according to the NVD record.

The fault is parsed while the engine works out the target service, before any per-service handler chain runs. Authentication handlers configured on a service therefore do not protect against it.

Am I affected?

NVD lists the affected range as:

  • Apache Axis 1.0 up to and including 1.4.
  • Any application that embeds or exposes Axis 1.x to inbound SOAP messages, including client code that parses SOAP faults.

The record is marked “unsupported when assigned”: Axis 1 is end of life. No fixed version exists, and the Axis project says it does not expect to release a fix for 1.x. The CISA entry also warns that affected products may be end-of-life and advises discontinuing use.

Technical details

  • Weakness: CWE-470, use of externally controlled input to select classes or code (unsafe reflection).
  • Attack vector: network, no privileges and no user interaction, which is how NVD arrives at a CVSS score of 9.8 (critical).
  • Exploitation: CISA lists it as known to be exploited. Whether it has been used in ransomware campaigns is listed as unknown.
  • EPSS: 1.77%, which is low, but KEV status outranks a prediction score.
  • Exploit conditions: a suitable class must be available on the application’s classpath. Which classes are being abused in the attacks has not been published.

Why this matters

This section is our analysis, not new reporting.

Axis 1.x is old middleware, and it often sits inside legacy Java applications, integration layers and vendor products where nobody remembers it is there. That makes the real exposure hard to measure from a package inventory alone.

Because authentication handlers run too late to help, an internet-reachable SOAP endpoint on Axis 1.x should be treated as exposed regardless of how it is secured. A flaw in CISA KEV with a three-day deadline belongs at the top of the queue: investigate within hours, not at the next patch cycle.

What to do

There is no vendor release to install. The Axis project recommends two routes, and the second is only for teams that must keep Axis 1 running:

  1. Find every Axis 1.x use. Search for axis-1.x JARs, org.apache.axis classes in application bundles, WAR files and vendor appliances, and ask suppliers which of their products embed it.
  2. Migrate to a different SOAP engine. The project suggests Apache Axis 2/Java.
  3. If you cannot migrate yet, build Axis with the upstream patch commit applied.
  4. Until then, limit who can reach SOAP endpoints on Axis 1.x. Remove them from the internet and restrict them to the callers that need them.
  5. Follow CISA’s required action if you fall under BOD 26-04: apply vendor mitigations, or stop using the product if mitigations are not available.

Detection and hunting ideas

No indicators of compromise have been published. These ideas follow from how the flaw works:

  • Review web and application logs for SOAP requests or responses containing a Fault with an unusual exceptionName, especially fully qualified class names that your application does not normally use.
  • Watch for Java processes spawning shells or unexpected child processes, and for new files written by the application server account.
  • Look for outbound connections from servers that host Axis-based services and normally do not initiate any.
  • CISA’s entry refers to forensics triage requirements, so preserve logs and memory from exposed hosts before rebuilding them.

What we do not know

The identity of the attackers, the targets and the scale of exploitation have not been published. The vendor advisory is a source-code commit and a mailing-list thread, and there is no separate fix announcement. This post will be updated if new details appear.

Related coverage

Sources

Spotted an error or outdated detail? Email contact@cyberstrikenews.com with the article link. We correct and note every change. Read our Editorial Policy.

Similar Posts