Skip to content
Server Security Center
KEVcritical9.8Unsupported product

CVE-2026-90436: Apache Axis Unsafe Reflection

Apache Axis · listed in the CISA catalog of actively exploited vulnerabilities since 2026-11-18.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
3.8%
higher than 90.3% of all CVEs
Added to CISA KEV
2026-11-18
US federal due date 2026-11-21
Ubuntu priority
high

CVE-2026-90436 explained

CVE-2026-90436 is an unsafe reflection flaw in Apache Axis 1.x, up to and including 1.4. When Axis processes an inbound SOAP fault, it loads and can instantiate a class named in the fault before checking its type. With a suitable class on the classpath, this can lead to unauthenticated remote code execution. Axis 1 is end of life, and the project does not plan a fixed 1.x release.

Impact

An unauthenticated remote attacker can make Axis load arbitrary classes, which runs their static initializers. Axis can also instantiate those classes through a String constructor. If a suitable class is on the application's classpath, this can lead to remote code execution with high impact on confidentiality, integrity and availability. No user interaction is needed. The fault is parsed before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. CISA lists the flaw as known exploited.

Who is affected

The axis source package is affected on Debian 12 (bookworm), Debian 13 (trixie) and the Debian testing distribution Debian 14 (forky). It is also affected on Ubuntu 16.04 LTS, 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS, 26.04 LTS and 26.10. No fixed version has been published for any of these releases. Ubuntu 16.04 LTS is end of life. Ubuntu 18.04 LTS and 20.04 LTS receive fixes only through Ubuntu Pro (ESM).

Written with AI from the data on this page and checked against it automatically.

Official description

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 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 github.com/apache/axis-axis1-java/commit/41f3b4e… applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Apache Software Foundation Apache Axis 1.x (EOL)
    Affected
    • ≤ 1.4
    Fixed in
    not stated

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Inventory all applications and systems that use the axis package or bundle Apache Axis 1.x libraries.
  2. Plan migration to a maintained SOAP engine, such as Apache Axis 2/Java, as the vendor recommends.
  3. Where migration is not yet possible, use an Axis build with the upstream patch applied.
  4. Restrict network access to Axis-based SOAP endpoints to trusted clients only.
  5. Upgrade systems on Ubuntu 16.04 LTS to a supported release.
  6. Restart affected applications after replacing or patching the Axis libraries.

No distribution has published a fixed axis package, and Apache does not expect to release a fixed Axis 1.x version. Remove axis where it is not needed. Otherwise, limit network exposure of SOAP endpoints to trusted sources. Use an Axis build with the upstream patch applied, and plan migration to a maintained SOAP engine. Do not rely on per-service authentication handlers for protection.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace axis with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="axis"'

No fixed version available

No Ubuntu or Debian release has published a fixed version of axis yet, so every installed version is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: lists.apache.org/thread.html/8slf0j9gz35z56t0glt5h0ncwlbn…
  • The vendor no longer supports the affected versions, so a fix may never come – plan the migration to a supported alternative.
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

Ubuntu 16.04 LTS has reached end of life and no longer gets regular security fixes – upgrade to a supported release.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-470 Use of Externally-Controlled input to select classes or code ('unsafe reflection')

Questions about CVE-2026-90436

Will a fixed Axis 1.x release be published?
No. The Apache Axis project does not expect to create an Axis 1.x release that fixes this problem. Axis 1 is end of life. The vendor recommends migrating to another SOAP engine, such as Apache Axis 2/Java, or using a build with the upstream patch applied.
Do authentication handlers on my services protect against this?
No. The malicious fault is parsed while the engine resolves the target service, before any per-service handler chain runs. Authentication handlers configured on a service therefore do not stop the attack.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-11-18, with a US federal due date of 2026-11-21. Whether it has been used in ransomware campaigns is unknown.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.