Security Resilience

CVE-2026-90436

Apache Axis 1.0 – 1.4

CISA KEVActive ExploitationEUVD Exploited
Published
06 November 2026
Modified
19 November 2026
KEV Added
18 November 2026
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.018 79th percentile
Risk Priority 97 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-90436 is a critical-severity Unsafe Reflection (CWE-470) vulnerability in Apache Axis. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 21% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

Advisories

EU & UK References

Vulnerability Data

** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. When a SOAP <Fault> carries a <detail><exceptionName> element, Axis loads the named class and, if a String <data> element is…

more

also present, instantiates it through its String constructor before checking that it is an AxisFault. Loading alone runs the class's static initializer. With a suitable class on the application's classpath this leads to remote code execution. The fault is parsed while the engine resolves the target service, before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. This affects all Apache Axis 1.x versions through 1.4. As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.

CWE(s)
KEV Date Added
18 November 2026

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-51441Same product: Apache Axis
CVE-2026-46718Same vendor: Apache
CVE-2026-86792Same vendor: Apache
CVE-2023-40743Same product: Apache Axis
CVE-2026-41871Same vendor: Apache
CVE-2026-82078Shared CWE-470both on KEV
CVE-2020-11978Same vendor: Apacheboth on KEV
CVE-2022-33891Same vendor: Apacheboth on KEV
CVE-2024-45195Same vendor: Apacheboth on KEV
CVE-2020-1956Same vendor: Apacheboth on KEV

Affected Assets

apache
axis
1.0 — 1.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Input validation directly stops externally supplied class or method names from selecting improper code via reflection.

Enforces authorization checks on the code or classes ultimately invoked, blocking unauthorized selections even if reflection is used.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly avoid introducing externally controlled class selection via reflection.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover unsafe reflection during code review or scanning.

PR.PS-05 partial match
blocks

Preventing execution of unauthorized code can block exploitation of unsafe reflection at runtime.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing can detect and block unsafe reflection patterns before release.

prevents

Training developers on secure coding practices (including reflection safety) reduces but does not eliminate unsafe reflection defects; the practice is fallible and the specific knowledge required is narrow, matching the A.6.3 -> CWE-598 and A.8.28 -> CWE-79 anchors.

prevents

Secure coding standards directly forbid unsafe reflection and require whitelisting or static alternatives.

prevents

A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and unsafe reflection is a regular software CWE introduced at design/implementation that those practices would address; the clause has a declared ceiling of `partial` on this verb, and the effect is real but a minority one because it depends on the supplier faithfully implementing secure coding.

finds

A.8.8's reach is DISCLOSURE — it surfaces only vulnerabilities published as advisories in third-party components. Unsafe reflection is a first-party code defect that requires source or runtime analysis to find, and A.8.8 sees only the minority of instances that surface as CVEs in third-party libraries (e.g., CVE-2018-1000613, CVE-2004-2331), not the bulk in first-party code.

References