Apache Axis 1.x: unauthenticated RCE CVE-2026-90436 (CISA KEV)
CISA confirms exploitation of CVE-2026-90436 in Apache Axis 1.x through 1.4: unauthenticated RCE via a SOAP fault. No fixed release is planned.

On 18 November 2026 the US CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities (KEV) catalog. It is a vulnerability in Apache Axis 1.x, the Apache project’s SOAP engine for Java. According to the National Vulnerability Database (NVD) description, an unauthenticated attacker can make the server load and instantiate Java classes of their choice and, with a suitable class present in the application, execute code remotely. Inclusion in the catalog means CISA has evidence of real-world exploitation.
This article is based on a single source: CISA’s KEV catalog entry, with NVD data. The entry does not say who is exploiting the flaw, against which organisations, since when or with which tools.
What the KEV entry says
- Name: Apache Axis Unsafe Reflection Vulnerability.
- Added to the catalog: 18 November 2026.
- Deadline for US federal agencies: 21 November 2026, three days after inclusion.
- Known use in ransomware campaigns: unknown («Unknown»).
- Required action: apply mitigations according to the vendor’s instructions, in line with CISA’s BOD 26-04 directive on prioritising security updates based on risk and its «Forensics Triage Requirements»; for cloud services follow the same directive, or discontinue use of the product if mitigations are unavailable. CISA also asks organisations to assess the internet exposure of every asset.
The reference to forensic triage requirements means that fixing the software is not enough: you also need to check whether the system has already been compromised.
Technical details
NVD describes the issue as deserialization of an inbound SOAP fault. When a SOAP message carries a <Fault> element with <detail><exceptionName>, Axis loads the class named in that field; if a String <data> element is also present, it instantiates the class through its String constructor, and only afterwards checks that it actually is an AxisFault.
According to the entry, this has two consequences:
- loading the class alone runs its static initializer;
- if a suitable class is on the application’s classpath, instantiation leads to remote code execution.
The most sensitive point concerns defences already in place: the fault is parsed while the engine resolves the target service, before the per-service handler chain runs. This is why authentication handlers configured on a service do not protect against this attack.
- Weakness: CWE-470, use of externally controlled input to select classes or code («unsafe reflection»).
- CVSS 3.1: 9.8 (critical), vector
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H: network attack, low complexity, no privileges required, no user interaction, high impact on confidentiality, integrity and availability. - NVD entry status: published on 6 November 2026, last modified on 18 November 2026, NVD analysis still in progress («Undergoing Analysis»).
The entry’s references include the commit with the fix in the apache/axis-axis1-java repository, a message on the Apache mailing lists and a message on the oss-security list dated 6 November 2026. In MITRE ATT&CK terms, exploiting a network-reachable service maps to T1190 (Exploit Public-Facing Application). The entry does not list any public indicators of compromise.
Affected versions and fix
According to NVD, all Apache Axis 1.x versions up to and including 1.4 are affected. The entry is marked «UNSUPPORTED WHEN ASSIGNED»: Axis 1 has reached end of life (EOL) and the Apache Axis project does not expect to publish a 1.x release fixing the problem.
The project points to two options:
- migrate to a different SOAP engine, such as Apache Axis2/Java (the project’s recommendation);
- alternatively, use a build of Axis with the patch from commit
41f3b4e8d04e310ca81f86b92630ab2c11d608bdin theapache/axis-axis1-javarepository.
What it means for European companies
Axis 1.x is a Java library: besides in-house SOAP services, it can sit inside third-party applications that bundle it without it showing up among installed software. Code execution in the application process puts at risk everything the application can reach: data, configuration, credentials for databases and other systems.
The KEV catalog is binding only on US federal agencies, but it is a widely used reference for prioritising updates. For organisations subject to NIS2 (in Italy, Legislative Decree 138/2024), a flaw with confirmed exploitation, a critical score and no official fixed version should be handled with top priority: for end-of-life components, risk management means replacement.
What to do now
- Inventory: look for Apache Axis 1.x in your SOAP services and in the applications that expose them, including libraries bundled in application packages. For third-party products, ask the vendor whether they include Axis 1.x and how they plan to address CVE-2026-90436.
- Fix: plan the migration to another SOAP engine, such as Apache Axis2/Java; in the meantime, consider a build with the patch indicated by the project. If neither option is viable, CISA says to discontinue use of the product.
- Exposure: assess whether SOAP endpoints are reachable from the internet or from untrusted networks and, until a fix is in place, consider restricting access to only the networks and systems that need it. Remember that per-service authentication handlers are not enough.
- Compromise assessment, as CISA requires with forensic triage: if you log the content of SOAP requests, look for inbound messages with a
<Fault>element containing<detail><exceptionName>; also check for processes started by the application’s user, new or modified files in the application folders and unusual outbound connections. - If you find suspicious signs, treat it as an incident: the fix does not remove access already gained. Consider the credentials used by the application exposed, rotate them and assess notification obligations.
How ARXDOME helps
ARX Expose shows what can be seen of your company from outside, with open ports, recognised products and known vulnerabilities on public services: it is the starting point to understand which endpoints are reachable from the internet. ARX Shield reports open vulnerabilities per machine and per package, with those already exploited highlighted. On monitored servers, ARX Sentry checks file integrity in the chosen folders and ARX Trace enables collection and searches across multiple machines to verify whether compromises have occurred.
Last updated:


