DEV Community

CVE-2026-90436 KEV Priorities: What Known Exploitation Changes for Defenders

CISA's decision to add CVE-2026-90436 to the Known Exploited Vulnerabilities catalog changes the priority signal. Apache Axis 1.x is end-of-life, the vulnerable request path is pre-authentication, and CISA has evidence of active exploitation.

That combination calls for rapid ownership checks even when a query returns an imperfect external count.

Vulnerability Overview

CVE-2026-90436 is an unsafe reflection flaw in Apache Axis 1.x through 1.4, classified as CWE-470. Apache does not plan a fixed Axis 1 release.

CISA added the CVE to KEV on November 18, 2026 and required covered federal agencies to apply mitigations under BOD 26-04 by November 21, 2026.

GitHub's NVD-linked advisory assigns CVSS 3.1 9.8. Atlassian rates a Confluence Data Center exposure path at CVSS 4.0 9.3.

The CISA mandate applies directly to covered federal agencies. Other organizations can use the risk signal without inventing a legal deadline that does not apply to them.

Mechanism and Exploitation Conditions

Axis parses a SOAP fault before the target service's handler chain. The fault can name a class through exceptionName and provide String data. Axis may initialize the class and invoke a String constructor before checking the object type.

A suitable class on the application classpath can turn that sequence into remote code execution. A service-level authentication rule may never see the request because the vulnerable parser runs earlier.

Reachability and classpath composition still affect exploitability. The reviewed material does not show that every Axis installation has the same exposure.

Impact

Code execution in the application process can affect confidentiality, integrity and availability. The attacker may reach data, credentials, integration endpoints and internal services available to the process.

The reviewed sources confirm known exploitation but do not identify a public victim count or prove that any external search result is compromised.

KEV status should change the order of work. Public-facing applications with a confirmed Axis 1 dependency and a reachable legacy SOAP path should move ahead of unsupported copies that are isolated and cannot be reached.

Affected Products and Scope

Every Apache Axis 1.x version through 1.4 is affected. Axis 2/Java is outside that version statement.

Confluence Data Center 1.x through 9.x is affected when Remote API (XML-RPC & SOAP) is enabled. Confluence Cloud is not affected, and Confluence 10.x and above do not contain the legacy feature.

The scope should include embedded dependencies and vendor packages. A product owner may need to supply a runtime classpath, build manifest or vendor confirmation because the library can be invisible from the outside.

Exposure Context

ZoomEye returned 176 successful matches for title="Apache Axis", 0 for app="Apache Axis" and 0 for vul.cve="CVE-2026-90436".

The title result is product-page evidence, not a confirmed vulnerable-asset count. The two zero results show limits in the selected fingerprints and CVE index, not proof of safety.

Combine the external observation with internal evidence. Confirm whether the displayed application is the affected code, whether the SOAP path is reachable, whether the classpath is suitable and whether the owner has applied the migration or patch. Record the query time and scope.

Remediation and Mitigations

Apache recommends migrating to a supported SOAP engine such as Axis2/Java. If migration cannot be completed immediately, a private Axis 1 build can apply commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd.

The absence of a vendor release means that owning that build and its tests is part of the risk reduction.

For Confluence Data Center, upgrade to 9.2.28 or later. If an emergency mitigation precedes the upgrade, disable Remote API, test dependent applications and verify that the legacy service path returns HTTP 403.

After patching, confirm the deployed version and required feature state rather than relying on a change ticket.

Defenders should record why a system is prioritized:

  • confirmed dependency
  • exposed path
  • classpath condition
  • known exploitation
  • business impact
  • verification status

That evidence makes the KEV decision auditable and prevents a broad title match from being reported as a confirmed compromise.

References

  • CISA Adds Four Known Exploited Vulnerabilities to Catalog
  • GitHub Advisory GHSA-988f-c54m-f8jj
  • Apache Axis vendor advisory thread
  • Atlassian advisory for CVE-2026-90436
Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.