CISA adds unsupported Apache Axis 1.x RCE to KEV

Conceptual legacy software joint between server modules with a message inspection gate.

A legacy dependency can remain a live trust path. Check Java SOAP services and vendor management applications for Axis 1.x rather than assuming an application login protects the parser.

What is new — November 18, 2026

CVE-2026-90436 is newly in CISA KEV. Apache’s vendor-authored CNA was published November 6, 2026 and rates the issue Critical; it supplies no numeric CVSS score. The new actionable fact is CISA-confirmed exploitation.

CISA added this CVE to KEV on November 18, 2026, establishing known exploitation. Ransomware use is listed as Unknown. A KEV entry does not establish compromise of any customer system.

Applicability and exposure

Apache says all Axis 1.x versions through 1.4 are affected. Inventory Maven dependencies axis:axis and org.apache.axis:axis and the runtime JAR actually loaded. An inbound SOAP fault can cause remote class loading and instantiation; RCE requires a suitable class on the application classpath. The fault is parsed before per-service handler chains, so authentication handlers configured on a service do not protect this path. Confirm endpoint reachability and actual component presence.

This is a shared-component alert. No product-specific exposure has been verified for Microsoft, VMware/Broadcom, N-able or another packaged vendor product. Do not copy this component range onto their product versions.

Remediation and its limits

Axis 1.x was unsupported when assigned. Apache expects no fixed Axis 1.x release and recommends migration to another SOAP engine, such as Axis2/Java. Its alternative is a build carrying commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd. That source patch is not proof of an available supported appliance update. Obtain the application vendor’s supported fix or migration plan; do not manually replace a bundled library in a vendor appliance.

CISA lists a November 21, 2026 federal deadline and forensicTriage: Yes, with ransomware use Unknown. The linked federal forensic implementation page was inaccessible; exact procedures were not verified. The deadline applies to covered federal obligations, not Brian’s customer-specific schedule. No vendor-directed blanket credential rotation or general workaround was verified.

Suggested MSP priority and action

Urgent for confirmed affected, reachable SOAP services. Inventory SBOM, runtime JAR and service exposure → restrict unnecessary access or isolate the endpoint where warranted → deploy a vendor-supported patched build or migrate from Axis 1.x → verify the deployed dependency, legitimate SOAP operations and authentication. Review relevant evidence and preserve it for incident response if suspicious activity is found. Ordinary service authentication is not a complete mitigation.

Official evidence

Apache-authored CNA record · Apache source patch · CISA official KEV data

Last verified November 18, 2026 ET. No customer component presence or compromise is assumed. Product-specific dependency linkage remains a separate validation task.

Share this article