Apache Axis 1.x: the unauthenticated SOAP flaw CVE-2026-90436 is exploited, with no fixed release planned

Top-Secured cyber watch: independent analysis based on the sources listed below. Top-Secured is not affiliated with the companies mentioned and will never ask you for your bank details or passwords.

On 18 November, CISA added CVE-2026-90436, a remote code execution flaw in the Apache Axis 1.x SOAP library that needs no authentication, to its catalogue of actively exploited vulnerabilities. Axis 1.x is end-of-life and the Apache project does not expect to publish a fixed release: affected applications must be migrated, rebuilt with the fix or isolated.

What happened

On 18 November 2026, the US agency CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities catalogue, which means it has evidence of attacks in the wild. The Apache Axis project disclosed the flaw on 6 November and rates it critical; CISA scores it 9.8 out of 10 (CVSS 3.1). CISA gives no detail on the attacks and says it does not know whether ransomware groups use the flaw. US federal agencies have until 21 November to act and must also check whether their systems were compromised beforehand.

Who is affected and how the attack works

Axis 1.x is an old Java library for SOAP web services. All versions up to 1.4 are affected, and CISA points out that the flaw can also sit inside third-party or commercial products that bundle the library. When Axis reads a SOAP fault containing an exceptionName element, it loads the class named by the sender and can create an instance of it before checking its type. If a suitable class is present on the application’s classpath, this leads to code execution. The message is processed before any service handler runs, so per-service authentication does not stop it: no credentials are needed.

Axis 1.x is no longer supported. The project says it does not expect to release a fixed 1.x version. It recommends moving to another SOAP engine such as Apache Axis2/Java, or using a build of Axis that includes its fix commit.

What to do now

  1. Look for Axis 1.x on your servers: find / -name '*axis*.jar' 2>/dev/null, then inside deployed archives: unzip -l app.war | grep -i axis. In Java projects, run mvn dependency:tree | grep axis (coordinates axis:axis and org.apache.axis:axis).
  2. Ask your software vendors whether their products ship Axis 1.x and when they will fix it.
  3. Migrate to a supported SOAP engine, or rebuild Axis with the project’s fix commit 41f3b4e8d04e.
  4. Until then, take Axis endpoints off the Internet: allow only known partners at the firewall or reverse proxy and disable services nobody uses.
  5. Check for signs of compromise: unexpected processes started by the Java application server, new files in web application folders, unusual outbound connections.

Our take

End-of-life components rarely show up in patch dashboards: they hide inside applications nobody touches any more. An inventory that goes down to the libraries, not just packages and services, is what lets you answer an alert like this one in an hour rather than a week.

Sources

How we choose, verify and write our analyses →

Is your own server exposed? Run a free check — public information only, no intrusion:

Check a server Check a website

Worried your servers are exposed? Our team audits, patches and monitors Linux and cloud infrastructure 24/7.

Talk to an expert Our managed server services →