Advisory

CVE-2026-90436: Critical Apache Axis 1.x Unsafe Reflection Enables Unauthenticated RCE

A critical unsafe reflection vulnerability in Apache Axis 1.x (all versions through 1.4) allows an unauthenticated remote attacker to load and instantiate an arbitrary class by sending a crafted SOAP fault message, potentially resulting in remote code execution. Because Apache Axis 1 is end-of-life and no new 1.x release is planned, affected organizations must migrate or apply the available patch immediately.

TL;DR: Apache Axis 1.x is end-of-life and actively exploited; migrate to Apache Axis 2/Java or apply the community patch from the upstream commit referenced in the NVD advisory without delay. CISA has added this vulnerability to the Known Exploited Vulnerabilities catalog and requires action under BOD 26-04.

What Is the Vulnerability?

CVE-2026-90436 is classified as an Unsafe Reflection vulnerability (CWE-470) in Apache Axis 1.x. It carries a CVSS 3.1 base score of 9.8 (CRITICAL) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating it is remotely exploitable with no authentication, no user interaction, and low attack complexity.

The flaw resides in how Axis 1.x processes inbound SOAP fault responses. When a SOAP <Fault> message carries a <detail><exceptionName> element, Axis uses Java reflection to load the class named in that element. If a <data> element containing a string value is also present, Axis attempts to instantiate the named class via its single-argument String constructor—before verifying that the resulting object is an AxisFault. Even if instantiation is not reached, the mere act of loading the class executes its static initializer.

Critically, this parsing occurs while the Axis engine is resolving the target service, before any per-service handler chain runs. This means authentication handlers configured on individual services provide no protection against this attack path.

Who and What Is Affected?

All versions of Apache Axis 1.x through 1.4 are affected. Apache Axis 1 is officially end-of-life (EOL)—a status that was already in effect when this vulnerability was assigned. The NVD entry carries the ** UNSUPPORTED WHEN ASSIGNED ** designation as a result.

Any application or system that:

  • Embeds or depends on the Apache Axis 1.x library,
  • Accepts inbound SOAP messages (including fault responses) from untrusted sources, or
  • Exposes an Axis 1.x endpoint reachable from a network

…is potentially at risk. Exposure is amplified when the application's classpath includes classes with side-effectful static initializers or single-argument String constructors that perform sensitive operations. The vulnerability requires no credentials and no prior foothold.

CISA added this CVE to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-18, indicating that exploitation in the wild has been confirmed.

Potential Impact

The CVSS vector reflects the worst-case outcome: complete compromise of confidentiality, integrity, and availability. With a suitable class already present on the application's classpath, a successful exploitation of this flaw could allow an attacker to:

  • Execute arbitrary code in the context of the Java process running Axis,
  • Read, modify, or delete data accessible to that process,
  • Disrupt availability of the service or underlying system,
  • Pivot to other systems reachable from the compromised host.

Because authentication handlers are bypassed at the fault-parsing stage, network-level controls and application-layer authentication configured within Axis itself do not mitigate the risk. Organizations should assume that any internet-facing or network-accessible Axis 1.x endpoint is exposed until mitigated.

The EOL status of Apache Axis 1 means that the Apache Axis project does not plan to release a 1.x patch. The risk is therefore persistent for any organization that does not act.

What to Do Now

Given the critical severity, confirmed exploitation (CISA KEV), and EOL status of Apache Axis 1, remediation should be treated as urgent. Prioritized actions:

  1. Migrate away from Apache Axis 1.x. The vendor's own guidance recommends transitioning to a supported SOAP engine such as Apache Axis 2/Java. This is the preferred long-term resolution.
  2. Apply the upstream patch if migration is not immediately possible. A patch commit is publicly available in the Apache Axis 1 Java repository: apache/axis-axis1-java commit 41f3b4e. Build and deploy a patched version of the library. Note that the Apache Axis project does not plan to distribute an official 1.x release containing this fix.
  3. Restrict network access. Where migration or patching cannot happen immediately, limit access to Axis endpoints at the network layer to only trusted sources. This reduces—but does not eliminate—exposure.
  4. Audit the classpath. Identify and, where possible, remove or restrict classes on the application classpath that have side-effectful static initializers or sensitive single-argument String constructors. This reduces the severity of a successful attack but is not a primary control.
  5. Follow CISA BOD 26-04 requirements. Federal agencies and organizations subject to CISA's Binding Operational Directive 26-04 must apply mitigations per the directive's timelines and forensics triage requirements. Consult the CISA KEV catalog entry for required action details.

Refer to the NVD advisory for CVE-2026-90436 and the CISA KEV catalog as primary references for the latest information.

How External Testing Surfaces This Exposure

Because this vulnerability exists in a specific library that may be embedded deep within a larger application stack, it can be easy to overlook during routine inventory reviews. External security testing helps in several ways:

  • Service fingerprinting: SOAP-based services exposing Axis 1.x can often be identified through characteristic WSDL structures, HTTP response headers, or error messages that reveal the underlying framework version. Identifying these endpoints is the first step toward knowing what requires remediation.
  • Dependency discovery: Point-in-time assessments of application components and their declared dependencies can surface Apache Axis 1.x inclusions, including transitive dependencies where Axis is bundled by a third-party library rather than directly referenced.
  • Exposure mapping: Understanding which Axis endpoints are reachable from external networks—versus internal-only—helps prioritize remediation sequencing. Internet-facing endpoints warrant the highest urgency given confirmed in-the-wild exploitation.
  • Patch verification: After applying the upstream patch or migrating to Axis 2, follow-on testing can confirm the patched behavior and that the vulnerable code path is no longer reachable.

Important note: Any testing should be conducted only against systems you own or have explicit written authorization to test, and should not involve sending live exploit payloads to production services.

Sources & further reading: NVD CVE-2026-90436 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: github.com, lists.apache.org, openwall.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Does configuring authentication on my Axis service protect against CVE-2026-90436?

No. According to the NVD advisory, the vulnerable fault-parsing code runs while the Axis engine resolves the target service, before any per-service handler chain executes. This means authentication handlers configured on individual services are bypassed entirely and do not protect against this attack.

Will Apache release an official Axis 1.x patch for this vulnerability?

No. The Apache Axis project has explicitly stated it does not expect to create an Axis 1.x release fixing this problem, because Axis 1 is end-of-life. A patch commit exists in the public repository and can be applied manually to build a fixed library, but no official 1.x release is planned. Migration to Apache Axis 2/Java is the vendor-recommended path.

Is this vulnerability being actively exploited?

Yes. CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities (KEV) catalog on 2026-11-18, which indicates that exploitation in the wild has been confirmed. Organizations should treat this as an urgent remediation priority.

My application uses Axis 1.x only internally, not exposed to the internet. Am I still at risk?

Reducing network exposure lowers the attack surface, but internal-only deployments are not risk-free. Attackers who have already gained a foothold on your internal network, or who can influence SOAP traffic flowing through internal systems, could still exploit this flaw. The recommendation to migrate or patch applies regardless of whether the endpoint is internet-facing, though internet-facing instances warrant the most immediate attention.