Apache Axis 1.x unauth RCE, actively exploited
Actively exploited
Risk assessment
Apache Axis 1.x through 1.4 lets unauthenticated attackers load arbitrary classes via a SOAP fault and achieve RCE. No fix coming; migrate to Axis 2 or apply the patch.
What to do
Apply the latest security patches from the vendor. If patching is not immediately possible, review the mitigation steps in this advisory and monitor for exploitation attempts.
- No fixed version listed yet. Restrict exposure and watch the vendor advisory. NVD references
- Remediation in this advisory
Actively exploited in the wild - CVE-2026-90436 is a critical unauthenticated remote code execution flaw in Apache Axis 1.x through 1.4 that lets attackers instantiate arbitrary classes from a SOAP fault before any service authentication handler runs. Apache has ended support for Axis 1 and will not ship a fixed release; migrate to Axis 2/Java or apply the upstream patch.
Overview
Apache Axis 1.x parses inbound SOAP <Fault> messages to resolve the target service, and it does so before any per-service handler chain executes. When a fault carries a <detail><exceptionName> element, Axis loads the named class. If a String <data> element is also present, Axis instantiates that class through its String constructor before ever checking that it is an AxisFault. Merely loading the class runs its static initializer, and instantiation runs the constructor.
The practical result is unauthenticated remote code execution. Attackers do not need credentials, and authentication handlers configured on a service provide no protection because the fault is parsed earlier in the request lifecycle. With a suitable class already present on the application’s classpath, the crafted fault triggers code execution on the server.
The vulnerability carries a CVSS score of 9.8 (network attack vector, low complexity, no privileges, no user interaction). CISA has added it to the Known Exploited Vulnerabilities catalog, confirming live attacks against internet-facing Axis 1 deployments. The EPSS score sits at 1.1 percent for the next 30 days, but that figure understates risk for any host still running the engine.
Impact
Any application exposing an Axis 1.x SOAP endpoint to an untrusted network is exposed. Successful exploitation gives an attacker arbitrary code execution under the application’s privileges, which typically means full control of the server, access to backend data stores, and a foothold for lateral movement. Because no authentication is required and the attack rides on normal SOAP traffic, it is easy to launch at scale.
Remediation
Apache considers Axis 1 end-of-life and does not plan an Axis 1.x release to fix this issue. Two options remain:
- Migrate to a supported SOAP engine such as Apache Axis 2/Java, or another actively maintained platform. This is the recommended path.
- Patch an existing build with the upstream fix from the project’s repository (commit
41f3b4e8d04e310ca81f86b92630ab2c11d608bd).
Until either is complete, restrict network access to Axis 1 endpoints, place them behind a reverse proxy that rejects malformed faults, and audit the application classpath for gadget classes that could be abused. Related reading: Apache ActiveMQ CVE-2026-34197 added to CISA KEV catalog.
Security Insight
Axis 1 joins a growing list of abandoned Apache components that remain deployed long after end-of-life, and the pattern is consistent: a parsing quirk turns into RCE precisely because the code is no longer maintained. The unauthenticated, pre-authentication nature of this bug mirrors the SOAP and deserialization failures that have hit enterprise middleware repeatedly over the past decade. That CISA is cataloging an EOL project’s flaw tells you defenders increasingly carry the burden the vendor has explicitly declined. See also GlassWorm attack uses stolen GitHub tokens for another case of neglected trust boundaries.
Further Reading
Exploit references 2 PoC Show
Public PoC References
Unverified third-party code
These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).
Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.
| Repository | Stars |
|---|---|
| fixedbyreboot/CVE-2026-90436-POC POC for CVE-2026-90436 - unauthenticated remote class instantiation in Apache Axis 1.x via SOAP fault exceptionName, bypassing configured auth handlers. EOL software, no fix exists. | ★ 2 |
| dinosn/axis-cve-2026-90436-lab-poc CVE-2026-90436 Apache Axis 1.x SOAP-fault unsafe reflection: Docker lab + PoC. Unauthenticated class instantiation/static-init on stock Axis 1.4, fires on any URL incl. undeployed services; stock impa | ★ 2 |
Showing 2 of 2 known references. Source: nomi-sec/PoC-in-GitHub.