CVE-2026-90436 was published in NVD on November 6, 2026. Twelve days later, on November 18, CISA added it to the KEV catalog with a deadline of November 21.
Here's the catch: there will be no fixed release. Apache Axis 1.x is end-of-life, and the project says so in the CVE description itself — it does not expect to ship an Axis 1.x release that fixes the problem. And Axis 1 is an embedded component: it hides inside Java applications, packaged software and appliances that don't always advertise it.
The Vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2026-90436 |
| CVSS 3.1 (CNA) | 9.8 (CRITICAL) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD score | not yet published (status Undergoing Analysis) |
| Type | Unsafe reflection — externally controlled class selection (CWE-470) |
| Authentication | none |
| Versions | all Apache Axis 1.x versions through 1.4 |
| NVD publication | 2026-11-06 |
| Added to CISA KEV | 2026-11-18 |
| CISA deadline | 2026-11-21 |
The CVE is tagged "UNSUPPORTED WHEN ASSIGNED": the product was already unmaintained when the ID was assigned.
How It Works
The NVD description is unusually specific. When Axis receives a SOAP message with a Fault element whose detail carries an exceptionName:
- Axis loads the class named in
exceptionName; - if a String
dataelement is also present, Axis instantiates that class through its String constructor; - only then does it check that the object is actually an
AxisFault.
Loading alone runs the class's static initializer. With a suitable class on the application's classpath, that becomes remote code execution.
The worst part is the timing: the Fault is parsed while the engine resolves the target service, before any per-service handler chain runs. In other words, authentication handlers configured on a service don't protect against it.
Exploitability therefore depends on what's on the classpath. It's the classic Java deserialization pattern: the more libraries an application ships, the better the odds an attacker finds a usable class.
No Fixed Release
| Option | What the CVE says |
|---|---|
| Fixed 1.x release | none: the project doesn't plan one |
| Migration | to a different SOAP engine, such as Apache Axis2/Java |
| Source patch | an Axis build with commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd from the apache/axis-axis1-java repository applied |
The KEV entry adds that the product may be end-of-life and advises discontinuing use or moving to a supported version. It also notes the flaw may affect third-party products that bundle the component — the hardest case, since each vendor has to ship its own update.
Detection
Step one is inventory: where does Axis 1.x live?
- Search application servers and WAR/EAR archives for
axis.jaroraxis-1.*.jar - In Maven or Gradle projects, look for the
axis:axis(ororg.apache.axis:axis) dependency - Query your SBOMs if you have them
- On the network side, find SOAP endpoints served by Axis, typically under
/axis/or/services/
find / -iname "axis*.jar" 2>&1 | grep -v "Permission denied"
For exploitation attempts: an inbound SOAP message containing a Fault with exceptionName is abnormal. Clients send requests, not Faults. Reverse proxy or WAF logs that keep request bodies may show it.
Mitigation
1. Migrate
It's the only lasting answer. Axis 1 won't get a fixed release.
2. Meanwhile: apply the source patch
If migration takes time, rebuild Axis with the commit cited in the CVE. For third-party products, ask the vendor whether they bundle Axis 1.x and when they'll ship a fix.
3. Reduce exposure
- Take SOAP services that don't need to be on the Internet off it
- Filter inbound SOAP requests containing a
Faultelement upstream (WAF, reverse proxy) - Don't rely on service-level authentication: the CVE states it doesn't kick in early enough
4. Triage
The KEV entry points to the forensic triage requirements of directive BOD 26-04: on any exposed server, look for unusual processes, files and outbound connections around the JVM.
Why Continuously Monitor Your Components
A flaw in an end-of-life component bundled into other products isn't solved by an update — it's solved by knowing where the component is. That inventory is best built before CISA gives you three days.
With cveo.tech, track your software and components with their versions, and get an alert as soon as a CVE affecting them lands in the CISA KEV catalog.