Apache Axis remote code execution flaw via crafted SOAP messages under active exploitation
On 18 November 2026 CISA added CVE-2026-90436, an unsafe reflection flaw in Apache Axis that allows unauthenticated remote code execution, to its Known Exploited Vulnerabilities catalogue. Any organisation running SOAP web services built on Axis, directly or inside third-party products, is concerned.
What to do now
- Product
- Apache Axis
- Affected versions
- Versions not specified by the source; the product may be end-of-life.
- CVE
- CVE-2026-90436
CISA has listed CVE-2026-90436, a vulnerability in Apache Axis, among the flaws it knows are being exploited in the wild. The bug is an unsafe reflection issue (CWE-470) that lets a remote attacker with no credentials run arbitrary code on the target server.
An attacker sends a crafted SOAP fault message, which causes Axis to load and instantiate a class of the attacker's choosing. Exploitation requires that a suitable class be present on the application's classpath, so real-world exposure depends on how each deployment is assembled.
CISA notes that the affected product may be end-of-life or end-of-service and advises users to stop using it or move to a supported version. The source does not list affected versions or name a fixed release; it points to a post on Apache's mailing lists for the vendor's guidance.
Because Axis is a library, the flaw can also sit inside third-party software that bundles it, sometimes without administrators being aware. CISA says it is not known whether the vulnerability has been used in ransomware campaigns.
US federal agencies must act by 21 November 2026 under directive BOD 26-04, which also requires forensic triage for this flaw. The short deadline and the triage requirement are a reminder that patching or removal alone is not enough: exposed servers should also be checked for signs that they have already been hit.
What to do now
- Inventory every server and application that uses Apache Axis, including third-party products that bundle it as a library.
- Remove Axis-based SOAP endpoints from internet exposure or tightly filter access to them until vendor mitigations are in place.
- Review Apache's mailing-list advisory and apply its guidance, or plan to retire Axis in favour of a maintained alternative.
- Inspect logs and system state on exposed Axis servers for unusual SOAP fault traffic, unexpected processes or other indicators of compromise.