CVE-2026-90436
Apache Axis 1.0 – 1.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS 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
- 🇪🇺 ENISA EUVD: EUVD-2026-118323
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
CVEs Like This One
Affected Assets
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.
Secure SDLC practices directly avoid introducing externally controlled class selection via reflection.
Vulnerability identification processes can discover unsafe reflection during code review or scanning.
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.
Security testing can detect and block unsafe reflection patterns before release.
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.
Secure coding standards directly forbid unsafe reflection and require whitelisting or static alternatives.
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.
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.