Skip to main content
Black Friday: 40% off your first 3 months on any monthly plan with code BF40. Ends Dec 2.See the offer
Varaxon Technologies

Known exploited vulnerability · CISA KEV

CVE-2026-90436: Apache Axis Unsafe Reflection Vulnerability

Apache Axis contains an unsafe reflection vulnerability that could allow an unauthenticated remote attacker to execute arbitrary code via a crafted SOAP fault message that causes Axis to load and instantiate an attacker-specified class when a suitable class is available on the application classpath. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.

CVE-2026-90436

Exploited in the wild. Fix this first.

CISA added it to the Known Exploited Vulnerabilities catalog on 2026-11-18: attackers are using it right now.

CISA KEV
Listed
Added 2026-11-18 · federal fix-by 2026-11-21
EPSS (30 days)
1.8%
Higher than 79% of CVEs · 2026-11-19Up 1.2% in 30 days
CVSS v3.1
9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What CISA says

Apache Axis Unsafe Reflection Vulnerability

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

NVD description · published 2026-11-06

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

Full record on NVD

Got a whole scan? Scan Hub runs this check on every finding in your Nessus, Qualys, Rapid7 or OpenVAS export and ranks the report by it.

Try it free

CVE-2026-90436 in plain words

Written by Varaxon from the sources below. Last checked .

What an attacker can do
Apache Axis 1.x reads an exceptionName from an incoming SOAP fault and loads that class, and if a text data element is present it also creates an object of that class, before checking that it is a real Axis fault. Loading a class runs its start-up code, so with a suitable class on the application's classpath an attacker with no account can run code. This happens before any per-service handler runs, so authentication set on a service does not protect against it.
Who is affected
All Apache Axis 1.x versions through 1.4, per the Apache Axis project. Axis 1 is end of life, and CISA notes it could be end of life or end of service. CISA notes the flaw can also affect other products that include Axis as a component.
What to do first
The Apache Axis project recommends moving to a different SOAP engine, such as Apache Axis2/Java, and says it does not expect to ship an Axis 1.x release that fixes this. The alternative it gives is a build of Axis with its published patch (commit 41f3b4e) applied. CISA advises stopping use or moving to a supported version, and asks US federal agencies to act by 2026-11-21.

How to check if you are exposed to CVE-2026-90436

  1. Find every Apache Axis system you or your clients run, including ones exposed to the internet. Those come first: CISA only lists flaws attackers are already using.
  2. Compare each version with the fixed versions in the vendor advisory below. Where no fix exists yet, apply the vendor’s mitigation or take the system off the internet.
  3. Run a credentialed vulnerability scan to catch the systems you missed, then check that the next scan no longer reports CVE-2026-90436.

US federal agencies had to fix this by 2026-11-21. Everyone else should treat that deadline as a guide: if it has passed, this is overdue.

Affected versions

Versions the National Vulnerability Database lists as vulnerable to CVE-2026-90436. Check the vendor advisory for the exact fixed builds before you sign anything off.

ProductVulnerable versions
Apache Axisfrom 1.0 up to and including 1.4

Timeline

  1. · Published in the National Vulnerability Database
  2. · Added to CISA's Known Exploited Vulnerabilities catalog, 12 days after it was published
  3. · Fix-by date for US federal agencies, still ahead

Vendor advisories and fixes

Weakness type

More exploited Apache vulnerabilities

CISA lists 42 exploited Apache vulnerabilities. The closest matches:

Keep going

Sources: CISA Known Exploited Vulnerabilities catalog (version 2026.11.18); EPSS data from FIRST.org; CVSS and descriptions from the NIST National Vulnerability Database. Checked 2026-11-20. This product uses the NVD API but is not endorsed or certified by the NVD.

Cookie preferences

Essential site functions remain available whichever option you choose. Your advertising choice is saved on this site. The Scan Hub has a separate choice.

Google and Reddit may receive cookies, identifiers, browser and device information, and your network/IP information. Reject or withdraw at any time. Read the Privacy Policy.