Skip to content
Security Alerts

CVE-2026-90436: RCE via SOAP Fault Message in Apache Axis 1.x (KEV)

The Apache Axis 1.x library loads and instantiates an attacker-specified class from a SOAP Fault message before service authentication runs. Axis 1 is no longer maintained and CISA confirms active exploitation...

Summary

ParameterValue
CVE IDCVE-2026-90436
Alert SourceCISA KEV - Active Exploitation
CVE Publication Year2026
Date Published2026-11-18
VendorApache Software Foundation
ProductAxis 1.x (SOAP engine for Java), all versions through 1.4
Vulnerability Typeunsafe reflection (CWE-470) → remote code execution
CVSS Score9.8 (critical)
EPSS Score1.1% (percentile: 67%)
CISA KEVYes - confirmed active exploitation
RansomwareNot confirmed
Remediation Deadline2026-11-21

Vulnerability Description

Source: NVD, Apache Axis (project mailing list), CISA KEV

When handling an inbound SOAP Fault, Apache Axis 1.x reads the <detail><exceptionName> element and loads the named class. If the message also contains a String <data> element, Axis instantiates the class 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. Authentication handlers configured on a service therefore do not protect against the attack, and the attacker does not need to be logged in. All Apache Axis 1.x versions through 1.4 are affected.

Axis 1 has been end-of-life for years. The CVE was assigned as “UNSUPPORTED WHEN ASSIGNED”, and the Apache Axis project does not plan a fixed 1.x release. CISA added the vulnerability to the KEV catalog on 18 November 2026, which means active exploitation has been confirmed.

Required Actions

  1. Inventory applications that bundle Axis 1.x (axis.jar, axis-1.4.jar in WEB-INF/lib directories and container images). Axis 1 is often embedded in older Java applications and third-party products — ask your vendors about their status.
  2. Migrate services to a different SOAP engine, such as Apache Axis2/Java — this is the Apache Axis project’s recommendation.
  3. If migration is not immediately possible, use an Axis 1.x build with the patch from commit 41f3b4e applied — the project will not ship it as an official release.
  4. Until fixed, restrict access to SOAP endpoints (network, WAF) and monitor SOAP Fault messages whose exceptionName element points to unexpected classes.
  5. If a service using Axis 1.x was reachable from the internet, check the application server for signs of compromise (new files, JVM child processes, outbound connections).

CISA set a remediation deadline of 21 November 2026 for US federal agencies.

Who Is Affected?

Organizations whose Java applications expose or consume SOAP services using Apache Axis 1.x (through 1.4) — especially older integration systems, line-of-business applications and third-party products with the library embedded. The CVE covers only the Axis 1.x line; the project points to Apache Axis2/Java as the replacement.

Sources


Need help securing your systems? nFlo team offers vulnerability management and 24/7 SOC services. Contact us.

Learn More

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Grzegorz Gnych

Grzegorz Gnych

Sales Representative

Response within 24 hours
Expert consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations