CVE-2026-90436 Validation Plan: Patching Axis Without Unsafe Live Testing
After an Apache Axis 1.x upgrade, removal or mitigation, the remaining question is whether the dangerous path is actually closed. CVE-2026-90436 crosses a library boundary, a service configuration and an application classpath. A validation plan should prove all three conditions without sending exploit code to a production system.
Vulnerability overview
CVE-2026-90436 is a critical unsafe reflection vulnerability in Apache Axis 1.x through 1.4. The Axis 1 branch is end-of-life, and Apache does not plan a fixed 1.x release. CISA added the CVE to KEV on November 18, 2026 based on evidence of active exploitation. GitHub's advisory records CVSS 3.1 9.8 and CWE-470.
Atlassian's Confluence Data Center advisory adds a deployment-specific condition. The legacy Remote API for XML-RPC and SOAP must be enabled for Confluence to be exposed. Atlassian lists 9.2.28 as the fixed version and rates the Confluence condition at CVSS 4.0 9.3.
Mechanism and exploitation conditions
Axis parses a SOAP fault before the service handler chain. An attacker-controlled exceptionName can cause class loading, and String data can cause a String constructor to run before the object is checked as an AxisFault. Static initialization may execute as part of class loading.
The final code-execution condition depends on the application classpath. A test that merely proves version 1.4 is present does not prove that a suitable class can be reached. A test that sends a full exploit to production also carries unnecessary operational risk.
Impact
Successful exploitation could run code with the application server's privileges. That can affect data, credentials, configuration and internal connectivity. A validation gap is dangerous because an administrator may believe the service is fixed while an old embedded jar, unpacked backup or secondary application node still loads the vulnerable parser.
The reviewed sources do not establish a universal live-test procedure or guarantee that removing one path eliminates every embedded copy. Validation should use deployment evidence and controlled environments.
Affected products and scope
Apache Axis 1.x through 1.4 is affected. Confluence Data Center 1.x through 9.x is affected only when Remote API is enabled. Confluence Cloud is not affected, and Confluence 10.x and above do not contain the legacy feature. Applications that bundle Axis need runtime-level confirmation.
Build pipelines should retain the resolved dependency graph and the artifact hash. Operations should record the deployed package, application-server classpath and configuration state. Both records are needed because a corrected source tree can still produce or deploy an older packaged dependency.
Exposure context
The successful ZoomEye queries were title="Apache Axis" with 176 matches, app="Apache Axis" with 0 and vul.cve="CVE-2026-90436" with 0. The title count is broad product-page evidence, not a vulnerable-instance count. The zero results do not prove that no affected application is reachable.
Use external matches to identify owners and follow up internally. For each candidate, validate the running artifact, the loaded classpath, the SOAP route, the Remote API setting and the patch or migration status. Keep evidence timestamps so a later deployment cannot be mistaken for the tested build.
Remediation and mitigations
The supported path is to remove Axis 1 and migrate to a maintained SOAP engine such as Axis2/Java. If a temporary private build is required, apply commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd and store the build provenance. Test API compatibility, authentication behavior and error handling in a controlled environment.
For Confluence, upgrade to 9.2.28 or later. When upgrading is not immediately possible, disable Remote API (XML-RPC & SOAP), test dependent add-ons and scripts, and verify that the legacy service path returns HTTP 403. The mitigation should be checked on every node that serves the application.
Validation should include a negative check that the vulnerable endpoint or library path is absent, a positive check that required business functions still work and a post-change inventory scan for the old artifact. Do not use exploit payloads against production systems. If an exploit test is necessary, run it only in an isolated environment under change control.
Close the change only when the owner can show which artifact is loaded, which configuration is active, which nodes were tested and how the result was reviewed. If those facts cannot be established, keep the system in the higher-risk state until evidence is available.
Top comments (0)