Exploited Apache Axis 1.x flaw CVE-2026-90436 allows unauthenticated code execution

Critical 9.8KEVCVE-2026-90436

Exploited Apache Axis 1.x flaw CVE-2026-90436 allows unauthenticated code execution

A critical flaw in Apache Axis 1.x, the end-of-life Java SOAP engine, can let an unauthenticated remote attacker execute code on the server. The bug, tracked as CVE-2026-90436, sits in how Axis handles inbound SOAP fault messages. A crafted fault can make Axis load and instantiate a class the attacker names. Simply loading a class runs its static initializer, and if a suitable class is on the application’s classpath, the result is remote code execution.

The flaw carries a CVSS score of 9.8. CISA added it to its Known Exploited Vulnerabilities (KEV) catalog on 2026-11-18, which confirms it is being exploited in the wild. Axis 1.x is no longer supported, and the Apache Axis project says it does not expect to publish a fixed 1.x release.

What’s affected

According to the NVD record, all Apache Axis 1.x versions through 1.4 are affected. The CVE was marked “unsupported when assigned” because Axis 1 is end-of-life.

Here is how the flaw works, as the record describes it:

  • When a SOAP <Fault> contains a <detail><exceptionName> element, Axis loads the named class.
  • If a String <data> element is also present, Axis creates an instance of the class through its String constructor.
  • Both steps happen before Axis checks that the class is actually an AxisFault.
  • The fault is parsed while the engine is still working out which service is being called, before any per-service handler chain runs. As a result, authentication handlers configured on a service do not protect against this flaw.

CISA notes that the vulnerability could affect open-source components or third-party libraries used by other products. Applications and vendor products that bundle Axis 1.x may therefore be exposed even if you never installed Axis directly.

How serious is it

The CNA rated the flaw 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain terms:

  • It can be attacked over the network.
  • The attack is not complex.
  • No login or privileges are needed.
  • No user interaction is needed.
  • A successful attack fully compromises the confidentiality, integrity and availability of the affected system.

Whether it leads to code execution depends on a suitable class being on the application’s classpath. Because loading a class alone runs its static initializer, administrators should not assume their deployment is safe.

Is it being exploited?

Yes. CISA added CVE-2026-90436 to the KEV catalog on 2026-11-18, confirming active exploitation. The KEV entry lists known use in ransomware campaigns as “Unknown”.

US federal civilian agencies must act by 2026-11-21. CISA’s required action is to apply mitigations in accordance with vendor instructions, in line with BOD 26-04 and CISA’s “Forensics Triage Requirements” guidance. Agencies should follow BOD 26-04 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. CISA also notes the product may be end-of-life and advises users to stop using it or move to a supported version.

What to do

  • Find Axis 1.x. Check your applications and third-party products for bundled Axis 1.x libraries, including within vendor software.
  • Migrate. Apache recommends moving to a different SOAP engine, such as Apache Axis 2/Java.
  • Patch if you cannot migrate yet. Alternatively, use a build of Axis with the upstream patch (commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd) applied. No official fixed Axis 1.x release is expected.
  • Restrict exposure. Limit network access to Axis SOAP endpoints, especially from the internet. Do not rely on service-level authentication handlers, which run too late to block this flaw.
  • Check for compromise. Given confirmed exploitation, review exposed systems for signs of compromise, following CISA’s forensics triage guidance where it applies to you.

References