Apache Axis Unsafe Reflection Vulnerability
TL;DR π
- Apache Axis contains an unsafe reflection vulnerability that could allow an unauthenticated remote attacker to execute arbitrary code via a crafted SOAP fault message that causes Axis to load and instantiate an attacker-specified class when a suitable class is available on the application classpath. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Usersβ¦
- Highest CVSS: 9.8 (Critical).
- Listed in CISA KEV (2026-11-18) β this is being exploited in the wild.
- Check the advisory for fixed releases β remediation detail is in the vendor link below.
- CVEs: CVE-2026-90436.
What it is
CVE-2026-90436 is an unsafe reflection flaw in Apache Axis 1.x, affecting all versions through 1.4. It sits in the SOAP engine’s handling of inbound fault messages, specifically in how Axis parses a <Fault> element’s <detail><exceptionName> field.
When a SOAP fault arrives, Axis loads the class named in exceptionName. Merely loading the class executes its static initialiser. If the fault also carries a string <data> element, Axis goes further and instantiates the class via its string constructor β before confirming the class is actually an AxisFault. Where a suitable class is present on the application’s classpath, this chain gives an attacker arbitrary code execution.
The access path is unauthenticated and over the network: the fault is parsed while Axis is still resolving the target service, ahead of any per-service handler chain. That means authentication handlers configured on a service provide no protection β the vulnerable code runs before they would be invoked. No credentials, prior session, or user interaction are required.
The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms a low-complexity, no-privilege, no-interaction network attack with full impact on confidentiality, integrity and availability. The CVE is in CISA’s KEV catalogue, added 18 November 2026, so it is known to be exploited. Axis 1 is end-of-life; the advisory notes the project does not expect to issue a fixed 1.x release.
What to do
- Treat any internet- or internally-reachable Axis 1.x SOAP endpoint as exposed regardless of service-level authentication configuration β the flaw triggers before those handlers run.
- Migrate to a supported SOAP engine, such as Apache Axis 2/Java, rather than waiting for an Axis 1.x fix β none is planned.
- If migration isn’t immediately possible, apply the patch from the commit referenced in the advisory (
41f3b4e8d04e310ca81f86b92630ab2c11d608bdin theapache/axis-axis1-javarepository) to a custom build. - As an interim mitigation, restrict network access to Axis endpoints (firewall rules, reverse proxy filtering) and inspect inbound SOAP traffic for fault messages containing
<detail><exceptionName>and<data>elements. - Given the KEV listing, prioritise this over routine patch cycles and check logs for SOAP fault messages carrying unexpected class names, as these would indicate exploitation attempts.
For leadership π§
Executive summary. Any Axis 1.x SOAP endpoint can be taken over remotely by an attacker who sends a single crafted fault message, with no login required and no protection from existing authentication settings. This is already listed as actively exploited and the product is end-of-life with no fix coming, so it needs emergency handling today, not the next patch window.
Why it matters:
- The vulnerable code path runs while Axis resolves the target service, before any per-service handler chain executes, so authentication configured on the service does nothing to stop this
- A crafted SOAP
with an exceptionName element causes class loading and static initialiser execution; adding a string data element triggers full instantiation, giving code execution where a suitable class sits on the classpath - CVSS 9.8 with no privileges, no user interaction and network access reflects a trivially reachable, fully remote compromise path against any exposed Axis 1.x service
- Apache has confirmed it will not release a fixed Axis 1.x version, so endpoints left running this component remain permanently exposed unless migrated or custom-patched
Now / Next / Later:
- Now: Identify every Axis 1.x SOAP endpoint reachable from the network and restrict access at the firewall or reverse proxy immediately, since service-level authentication offers no protection here.
- Next: In the next change window, either migrate affected services to Apache Axis 2/Java or build and deploy Axis 1.x with the referenced patch commit applied, and check logs for SOAP faults carrying unexpected exceptionName or data values.
- Later: Retire Axis 1.x entirely as part of a planned migration to a supported SOAP stack, since no further security fixes will be issued for this end-of-life component.