Apache Axis Security Vulnerability: Which Java Applications You Should Isolate, Patch, or Replace Now

Apache Axis Security Vulnerability: Which Java Applications You Should Isolate, Patch, or Replace Now

The Apache Axis security vulnerability CVE-2026-90436 affects a SOAP library for Java whose last version was released in 2006 and for which Apache no longer publishes fixes. Exploit code has been public since November 12, and according to security firms it was used to take over N-central servers. Those affected are IT managers and application owners in manufacturing, intralogistics and retail who run Confluence Data Center, older vendor products or their own Java applications with SOAP interfaces, as well as managed service providers.

Short answer

Apache Axis 1.x through version 1.4 remains permanently vulnerable. First, identify all Java applications that contain Axis 1.x. Vendor products will receive the vendor’s fix or be isolated. For in-house developments, use a custom-built Axis implementation with the Apache patch as a temporary solution, and plan to migrate to a maintained SOAP library or phase out the application in the 2027 budget.

Affected Software and Fixes, as of November 14, 2026. Sources: Apache Software Foundation, CVE entry with CISA assessment, Atlassian, Debian Security Tracker, SecurityWeek
Software Affected Fix Exploitation
Apache Axis 1.x All versions up to 1.4 No new version, just a patch to the source code Proof of concept public
Confluence Data Center 1.x through 9.x with Remote API enabled (XML-RPC and SOAP) Version 9.2.28 or 10.x No information provided by Atlassian
N-able N-central Server with Legacy API enabled, even with Hotfix 2 Disable the legacy API; additional fixes are in progress Proof of concept public, security firms report 21 compromised servers
Debian package axis Debian 12, 13, testing, and unstable None yet Not specified

What Is Known About the Apache Axis Security Vulnerability

On November 6, 2026, the Apache Project published CVE-2026-90436. Axis 1.x processes incoming SOAP error messages in such a way that an unauthenticated attacker can cause Java classes to be loaded. If a suitable class is present in the application’s classpath, this leads to code execution. Authentication at the individual web service does not provide protection because Axis processes the message beforehand. Apache recommends switching to a different SOAP library, such as Apache Axis2/Java, or using a custom build with the published patch (Apache via oss-security, November 6, 2026). The latest version, Axis 1.4, was released on April 22, 2006 (Apache Axis).

CISA rates the vulnerability in the CVE entry at 9.8 points according to CVSS 3.1 (CVE-2026-90436). Red Hat rates it lower because the attack requires a matching class to be present in the classpath. Atlassian has fixed the issue in Confluence Data Center version 9.2.28 and rates the vulnerability at 9.3 points according to CVSS 4.0 (Atlassian, November 2026).

On November 12, exploit code was published that chains the vulnerability with a flaw in N-central. According to SecurityWeek, Huntback and Lupovis found a few hours later that attackers had taken over 21 N-central servers and installed crypto miners, including servers in Germany (SecurityWeek, November 13, 2026).

2006

Axis 1.4 marked the final release of Apache Axis 1. The project has no plans to release a corrected version.

Apache Axis, April 2006, and Apache, November 2026

What Is Proven and What Is NotThe Hungarian cybersecurity agency NKI has listed exploitation of the vulnerability since November 12, and the Italian CSIRT reported it on November 13 (CSIRT Italia, November 13, 2026, NKI Hungary, November 2026). It is not listed in the CISA catalog of actively exploited vulnerabilities dated November 13, 2026. It is unclear which other vendor products contain Axis 1.x. Atlassian has assigned Confluence to this vulnerability. For N-central, the assignment comes from the researcher who published the exploit code.

What the Vulnerability Means for Legacy Java Applications in Manufacturing and Retail

According to the project website, many companies have integrated Axis 1 into their products. In industry, this includes supplier portals, EDI adapters, interfaces to MES and PLM systems, or services that report test bench data to the ERP system. In retail, these might include legacy integrations with merchandise management and store systems. In day-to-day operations, the library rarely draws attention because it is located in the application folder as the file axis.jar or axis-1.4.jar.

The CVE entry lists the Maven coordinates `axis:axis` and `org.apache.axis:axis`. Using a software bill of materials (SBOM) or a file search on the application servers, the inventory can therefore be completed in a matter of days.

A model calculation illustrates the scale of the project. Consider a mechanical engineering company with two plants and 30 Java applications. The inventory is estimated to take 3 to 5 person-days. The system includes Confluence Data Center 8.x with the Remote API enabled, a PLM connector from a vendor with no announced fix, and three in-house developments: a supplier portal, an EDI adapter, and a plant service. We estimate that updating Confluence to 9.2.28, including testing, will take 3 to 6 person-days, and isolating the connector will take 1 to 2 person-days. For each of the three in-house developments, we estimate 1 to 2 person-days for a build using the Apache patch. Immediate measures are therefore estimated to cost 10 to 19 person-days. The conversion of the three in-house developments to a maintained SOAP library adds an estimated 10 to 25 person-days per application, for a total of 30 to 75.

Apply a patch, isolate the system, or replace Axis 1.4: Your options

Options, our own assessment, as of November 14, 2026
Option Effort Costs Risk
Install the vendor's fix Hours to days per product Low to moderate Only for products whose vendor ships a fix
Disable the SOAP interface, such as the Remote API or Legacy API Hours Low Scripts, automations, and add-ons that use them stop working
Isolate, SOAP endpoint reachable only from known networks 1 to 2 person-days per application (estimate) Low The vulnerability remains, attackers on the internal network can still reach it
Custom build with the Apache patch 1 to 2 person-days per application (estimate) Low You maintain your own fork of a library without further development
Migration to a well-maintained SOAP library 10 to 25 person-days per application (estimate) Medium Interfaces must be retested with all connected systems
Replace the application Months High It's worth it if the application contains other outdated modules
Do nothing None None for now Code execution on the application server without authentication

The vendor's instructions are authoritative. Test updates in a test environment first. How we replace legacy applications step by step without stopping operations is described on the page Legacy Modernization with a Migration Plan.

Which method is best suited for which application?

Atlassian has outlined the procedure for Confluence Data Center. According to Atlassian, if the Remote API is disabled, the instance is not vulnerable; otherwise, update to version 9.2.28 or 10.x. For third-party products without an announced fix, isolate them and request a timeline in writing.

For in-house developments, the build with the Apache patch offers the fastest protection. We consider it a stopgap solution for a few months. Anyone who runs it long-term is maintaining a library whose latest version was released in 2006. The migration is worth it for applications that need to keep running. It’s better to phase out applications with outdated Java, application servers, and database drivers, because the next vulnerability will likely be found in a different library.

Legacy Check for Java Applications in Ten Business DaysWe identify all Java applications at your locations that use Axis 1.x and other libraries that are no longer supported, assess the availability of their SOAP endpoints, and determine the status of vendor fixes. For each application, you’ll receive a recommendation to patch, isolate, refactor, or replace it, along with an estimated effort and a prioritized schedule for the coming weeks. You can then decide which applications to bridge and which to include in the 2027 modernization budget.

Request a Legacy Check

Frequently Asked Questions

How can I find out if CVE-2026-90436 affects any of our applications?

Search the application servers for files such as axis.jar or axis-1.4.jar, and search the dependency lists for the Maven names axis:axis and org.apache.axis:axis. For third-party products, refer to the manufacturer's instructions.

How much does it cost to modernize a SOAP interface?

In our model calculation, the cost of migrating an in-house development to a well-maintained SOAP library is estimated at 10 to 25 person-days. We allocate the majority of this time to testing with suppliers, ERP systems, and plant systems.

Is Confluence affected without the Remote API?

No. According to Atlassian, Confluence Data Center is only affected if the Remote API for XML-RPC and SOAP is enabled. For new installations, it has been disabled by default since version 3.0, and Atlassian removed it in version 10.0.

The Next Step

For the inventory, interim protection and refactoring of legacy Java applications, support comes from our Legacy Modernization with a Migration Plan. If you're running N-central, you can find the steps for the server in Check for and Fix the N-central Security Vulnerability. A similar case without a new version is PHP2Shell in PHP 8.1 and earlier, for Java interfaces in SAP systems, see Replacement of SAP PO Before 2030. Schedule an Initial Consultation.

Questions about this post?

Just a couple of sentences about your situation will suffice. The person responding builds these kinds of systems himself.

We'll respond within one business day.torck · Code mit Drehmoment
Florian Blischke
Managing Director at torck · Over 20 years of software development experience
Florian Blischke is the managing director of torck, based in Maxhütte-Haidhof near Regensburg. He has been working in software development for over 20 years. His focus is custom software, data and AI for industry and retail, ranging from the integration of physical processes and IoT to cloud architecture and data- and AI-driven systems. torck works with its own nearshore team in Rabat. At torck, he oversees projects including the Jouvoli energy platform and the KVM Fleet fleet management product. torck develops software at its locations in Maxhütte-Haidhof, Vienna and Rabat and focuses on software that actually works in operation.

Are you facing the same question?

Since 2017, we have been building software for industry and retail from Maxhütte-Haidhof near Regensburg, with teams in Vienna and Rabat. An initial consultation takes 30 minutes and costs nothing. Afterwards you will know whether the project is worth pursuing, even if the answer is no.

More Articles