What changed
CISA now records exploitation of an old component
On 18 November, CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities catalog. A crafted SOAP fault can make Apache Axis 1 load and instantiate an attacker-specified class when a suitable class is present on the application classpath. That can lead to unauthenticated code execution. Axis 1 is end of life, and applications that embed it need their own exposure and remediation check.
Confluence Data Center is one concrete example. Atlassian says versions before Confluence 10 can be affected only when the legacy Remote API for XML-RPC and SOAP is enabled; Confluence Cloud and 10.x are not affected by this product path. The vendor lists 9.2.28 as a fixed release. Those conditions should not be projected onto every other application using Axis.
Look inside the application
Defender workflow
Find the dependency and the exposed endpoint
- 1
Locate Axis 1. Search application inventories and Java archives for Axis 1, then map each instance to the service, owner and reachable SOAP endpoint.
- 2
Apply product-specific guidance. For Confluence Data Center, check the Remote API setting and upgrade to the vendor's fixed build. Disabling the legacy API can reduce exposure while testing the upgrade, but may affect integrations.
- 3
Investigate server behavior. Review unusual SOAP fault traffic, Java process activity and unexpected classes or child processes. An upgrade does not answer whether an already exposed server was used.
Defender note
A library version is only the first layer
Because the exploit depends on the classpath and an exposed SOAP handler, the same Axis jar can carry different practical risk in two products. Record the product context with the dependency finding, then prioritize the reachable management and collaboration systems first.