Security alerts · November 18, 2026

Apache Axis 1.x: critical flaw may allow code execution on servers without login

A critical flaw, CVE-2026-90436, in the Apache Axis 1.x Java library (CVSS 9.8) may let an attacker run code on a server without logging in if a suitable class is present. EUVD lists it as exploited. Axis 1.x is end of life with no fix release planned. Migrate to another SOAP engine or apply the source patch.

Updates

November 19, 2026: On November 18, 2026, CVE-2026-90436 was added to the CISA KEV catalog, which means attackers are now actively exploiting it. If you have not updated yet, make it a priority.

What happened

Apache Axis 1.x is an older Java library that applications use to offer and call web services over the SOAP protocol. Many legacy business applications rely on it, and it is often bundled inside third-party products without administrators being aware of it.

On November 6, 2026, the Apache project published a critical vulnerability, CVE-2026-90436, on the oss-security mailing list. Over the network and without logging in, an attacker can make the server load and create a class (a piece of program code) of their choosing. According to Apache, if a suitable class is available to the application, this leads to remote code execution on the server. The flaw was found by José Apari-Pantigozo of OKIOK.

The catch is that Axis 1.x is end of life (EOL). The Apache Axis project does not expect to release a fixed 1.x version. The fix exists only as a change in the source code.

The EU Vulnerability Database (EUVD), run by ENISA, lists this flaw (EUVD-2026-118323) as exploited since November 18, 2026. Apache’s own announcement does not mention exploitation.

Why it is dangerous

The flaw falls under CWE-470: using outside input to choose which class or code gets run. Picture a receptionist who takes a name card from a stranger and lets them into the building before checking whether they are allowed in at all. When Axis 1.x processes a SOAP fault message arriving from the network, it loads a class whose name was chosen by the sender and only then checks whether it is an allowed type. In Java, merely loading a class runs its initialization code.

According to Apache, this message is processed before any service-specific rules apply. Authentication configured on individual services therefore does not protect against it. The attack works over the network, and the attacker needs neither an account nor any action by a user.

According to Apache, the attack leads to code execution only if a suitable class is on the application’s classpath. In enterprise applications with many libraries, this condition cannot be ruled out in advance. If the attack succeeds, the attacker runs their own code with the application’s privileges. They could then reach the data and passwords the application uses and try to move further into the internal network.

  • CVSS 9.8 out of 10 (critical): the technical severity. The attack is network-based, easy to perform, requires no login or user action, and can affect confidentiality, integrity and availability. The score in the NVD record was not assigned by NVD itself but by another organization listed in the record.
  • EPSS about 1.1% (as of November 18, 2026): a statistical estimate of the chance of exploitation within the next 30 days. It is higher than for roughly 67% of known vulnerabilities. A low number does not mean safety, as EUVD already lists exploitation.
  • EUVD: ENISA’s EU Vulnerability Database, which lists this flaw as exploited since November 18, 2026.

Who is affected

All Apache Axis 1.x versions through 1.4 are affected. Apache also lists development builds from the repository starting at commit aac718c6035435d96b39d6aebb9c078a13af7cc8 before fix 41f3b4e8d04e310ca81f86b92630ab2c11d608bd.

Axis 1.x runs inside Java applications on application servers such as Apache Tomcat, JBoss/WildFly, WebLogic or WebSphere. You will typically find it in older line-of-business systems, SOAP integrations between company systems, and off-the-shelf third-party products. The highest risk is where the web service is reachable from the internet, for example for partners or branch offices.

The advisory covers Axis 1.x only. Apache Axis2/Java is a separate SOAP engine, and Apache recommends it as a replacement.

How to check if you are affected

Look for Axis 1.x library files on servers running Java applications. The following commands only read data and change nothing. On Linux:

find / -type f \( -name "axis.jar" -o -name "axis-1*.jar" \) 2>/dev/null

The library is often packed inside .war, .ear or executable .jar archives. This command lists archives that contain Axis 1.x (not Axis2):

find / -type f \( -name "*.war" -o -name "*.ear" -o -name "*.jar" \) 2>/dev/null | while read -r f; do unzip -l "$f" 2>/dev/null | grep -qE 'org/apache/axis/client/|(WEB-INF|BOOT-INF)/lib/axis[-.]' && echo "$f"; done

The version is shown in the file name (for example axis-1.4.jar) or in its manifest:

unzip -p /path/to/axis.jar META-INF/MANIFEST.MF

If Axis was installed from distribution packages:

dpkg -l | grep -i axis
rpm -qa | grep -i axis

On Windows servers, in PowerShell:

Get-ChildItem -Path C:\ -Recurse -Include axis.jar,axis-1*.jar -ErrorAction SilentlyContinue | Select-Object FullName

For third-party products, ask the vendor whether they ship Axis 1.x and how they are addressing CVE-2026-90436.

How to fix it

No fixed Axis 1.x release is coming. Apache recommends migrating to a different SOAP engine, such as Apache Axis2/Java. As an alternative, it points to building Axis with the patch from commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd in the project’s GitHub repository.

Recommended order of steps:

  • Inventory: identify every application and server using Axis 1.x, including third-party products.
  • Limit exposure right away: services built on Axis 1.x should not be reachable from the internet. Allow access only from specific partner IP addresses or over VPN. This is our general advice. Apache does not list a workaround.
  • Short term: if you own the application’s source code, have your developers build Axis with the patch from the commit above and deploy it after testing.
  • For third-party products, ask the vendor for a fixed version or their guidance.
  • Long term: plan a migration to a supported SOAP engine such as Apache Axis2/Java. Axis 1.x is unsupported and further flaws will not be fixed.

According to Apache, authentication configured on individual Axis services does not protect against this flaw. Do not rely on it as a stopgap.

What if you may already be compromised

Apache’s announcement lists no specific indicators of compromise. Since EUVD lists the flaw as exploited, it is worth checking internet-facing systems for traces, especially over the past few weeks.

  • Application server access logs: unusual POST requests to Axis service paths (often containing /axis/ or /services/) from unknown IP addresses.
  • Application logs: unusual errors while processing SOAP messages or loading classes.
  • Processes: shells, cmd.exe, curl, wget or PowerShell started by the Java server process.
  • Files: new or modified .jsp or .jar files or scripts in web directories and temporary folders.
  • Accounts and connections: new user accounts, new scheduled tasks and unexpected outbound connections from the server.

If you find any of these, disconnect the server from the network but do not shut it down or delete files, so evidence is preserved. Bring in an incident response specialist and change the passwords and keys the server had access to.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.