Our Thinking / Field Notes / The Security Watch

EVOLVING SECURITY ADVISORY / APACHE AXIS 1.X UNSAFE REFLECTION VULNERABILITY (CVE-2026-90436)

Apache Axis 1.x Remote Code Execution Flaw: Are You at Risk?

CVE-2026-90436 lets an unauthenticated attacker run code through Apache Axis 1.x, which has no fixed release and is being actively exploited. Who is exposed, what to check first and how to respond.

What matters now

Current position: Critical. No fixed Apache Axis 1.x release is planned; vendor-specific fixes exist for Confluence Data Center (9.2.28) and N-central (2026.4 HF3).

Affected versions: Apache Axis 1.x through 1.4 and source builds before commit 41f3b4e8. Confluence Data Center with Remote API (XML-RPC & SOAP) enabled (fix version listed: 9.2.28; removed in 10.0). Self-hosted N-central with Legacy API enabled (2026.4 HF3 disables it).

Observed exploitation: Active exploitation: listed in CISA's Known Exploited Vulnerabilities catalogue on 18 November 2026; Rapid7 reports exploitation against Confluence Data Center and N-able N-central.

Recommended next action: Identify anything using Axis 1. Upgrade or isolate internet-facing Confluence Data Center and N-central first, remove or restrict SOAP endpoints elsewhere, then check exposed systems for compromise since 6 November 2026.

Identifiers: CVE-2026-90436

Immediate guidance

CVE-2026-90436 is a critical flaw in Apache Axis 1.x (all versions up to 1.4) that can let an unauthenticated attacker run code remotely. CISA added it to its Known Exploited Vulnerabilities catalogue on 18 November 2026. Axis 1 is end-of-life and Apache does not plan a fixed 1.x release, so the lasting fix is to migrate to a different SOAP engine or build Axis with Apache's patch commit. Today, find out whether you run Confluence Data Center, a self-hosted N-able N-central or any Java application that bundles Axis 1. Fix or isolate anything internet-facing first, then check it for signs of compromise.

What to do first (as of 22 November 2026)

The vulnerability is tracked as CVE-2026-90436. Apache Axis is a long-retired Java library for building and calling SOAP web services, and plenty of older business software still carries a copy inside it. You may never have installed Axis yourself and still be running it.

The order of work is straightforward. Find out whether anything you run uses Axis 1. Deal with anything reachable from the internet first. Then, for those systems, look for signs that someone got in between 6 November (when the flaw was disclosed) and the day you fixed or isolated them. Patching closes the door but does not evict anyone who has already walked through it.

Information is still developing, particularly around which other products embed Axis. Treat the product list below as the confirmed cases, not the complete set.

  • Confluence Data Center: Atlassian lists 9.2.28 as the fixed version. Version 10.0 and later removed the affected feature.
  • Self-hosted N-able N-central: Rapid7 advises moving to 2026.4 HF3 (build 2026.4.1.39) as an emergency change.
  • Anything else running Java: search for Axis 1 files (steps further down) and ask your software suppliers whether their product embeds it.

What is affected

Apache's advisory covers Apache Axis 1.x up to and including 1.4, plus builds from the source repository older than patch commit 41f3b4e8. The CVE record lists the Maven packages axis:axis and org.apache.axis:axis. Axis 2 is a separate project and is not named in the advisory, so a file called axis2-something.jar is not what you are looking for.

The flaw is in how Axis reads an incoming SOAP fault, which is the error message a SOAP service returns. Axis loads whatever class the message names, and if a String data element is present it also creates an instance of that class before checking it is a genuine Axis fault. Simply loading a class runs its startup code, so if a suitable class exists in the application, an attacker may get code execution. The advisory adds that the fault is parsed before any service-level authentication handler runs, so adding authentication to your service does not protect you.

Two practical consequences. First, exposure depends on your application as well as on Axis, because a usable class has to be available. Do not rely on that: a Metasploit module for Confluence was released on 17 November and exploitation has been observed. Second, because the problem sits in fault parsing, an Axis 1 application that calls out to other SOAP services could in principle be exposed to a hostile or compromised remote service. Apache's description does not spell that out, so take it as a reason to include client-side uses in your inventory, not as a confirmed attack path.

How serious it is

CISA's analysis in the CVE record scores it 9.8 (critical) with no authentication, no user interaction and network access. Atlassian rates its own Confluence ticket 9.3 under CVSS 4.0. CVSS measures how bad a flaw could be, not how likely an attack is, but in this case there is direct evidence of attack as well.

CISA's catalogue entry is titled Apache Axis Unsafe Reflection Vulnerability, which is the weakness class CWE-470. The CVE record also carries CISA's assessment that exploitation is active, that it can be automated and that the technical impact is total. Rapid7 reports exploitation against Confluence Data Center and N-able N-central, covered in the sections below.

CISA's remediation due date for US federal agencies was 21 November 2026. It does not bind UK organisations, but it is a fair indication of how urgently the authority treats this.

Find out whether you run Axis 1

Start with products you know about, then search servers for the library itself. Both searches below only read file names. They can take a while on a large disk, so point them at the application directories first. A search finds standalone Axis files only; copies packed inside another archive or merged into a single jar will not appear, so your supplier's answer matters as much as the search result.

Developers can check build files and dependency lists for the axis:axis or org.apache.axis:axis coordinates.

  1. List the internet-facing systems you run that use Java, particularly Confluence Data Center, N-central and any bespoke application with a SOAP interface. These are the ones to settle first.
  2. On Linux servers, run this as a user who can read the application directories. It lists any file named axis.jar or axis-1 followed by anything, which is how Axis 1 is normally distributed.
    bash
    find / -type f \( -name 'axis.jar' -o -name 'axis-1*.jar' \) 2>/dev/null
  3. On Windows servers, run this in PowerShell with rights to read the application folders. Replace C:\ with a narrower path first if you want a quicker pass.
    powershell
    Get-ChildItem -Path C:\ -Recurse -Include 'axis.jar','axis-1*.jar' -ErrorAction SilentlyContinue | Select-Object FullName, LastWriteTime
  4. Write down each hit with its server and owner. Anything found in a product you did not build yourself needs a question to the supplier: does this product use Axis 1 and is there a fixed release?

Confluence Data Center and N-central

Atlassian's ticket for Confluence Data Center says an instance is only vulnerable if the setting Remote API (XML-RPC & SOAP) is enabled. That setting has been off by default for new installations since Confluence 3.0 and the feature was removed entirely in 10.0, so older upgraded sites are the likeliest to have it on. Atlassian lists 9.2.28 as the fix version (resolved 10 November 2026). Rapid7 reports that Atlassian Cloud is not affected. If you run a different 9.x branch, check Atlassian's ticket and bulletin for the fixed build for that branch before assuming 9.2.28 applies.

Atlassian's ticket lists no workaround. Rapid7 notes that if you cannot upgrade immediately you can clear the Remote API setting in the administration console, with the caveat that anything using the XML-RPC or SOAP API will stop working. Check what depends on it before you change it, and test the change on a non-critical instance if you have one. Afterwards, confirm the setting is unticked and that the integrations you expected to break have in fact stopped, because that tells you the change took effect.

For self-hosted N-central, Rapid7 identifies the Legacy API feature as the exposed surface. Version 2026.4 HF3 (2026.4.1.39), released 16 November, disables it, and Rapid7 advises upgrading on an emergency basis. It also advises on-premises administrators to confirm Legacy API is off even if they are already on 2026.4 HF2. In our judgement this one deserves speed: a remote management platform holds credentials and reach across many other machines, so a compromise rarely stays confined to one server. Note that N-able's own communications do not appear to name this CVE, so follow N-able's hotfix instructions and release notes for the upgrade itself.

Fixing your own or a supplier's Axis 1 application

There is no patched Axis 1.x release to download. Apache says Axis 1 is end-of-life and the project does not plan a release that fixes this. The advisory recommends migrating to a different SOAP engine, such as Apache Axis 2/Java, or building Axis with the patch from commit 41f3b4e8d04e310ca81f86b92630ab2c11d608bd. Building from a commit is a development task: whoever owns the application needs to rebuild, test and redeploy it, so treat it as a planned change, not a quick hotfix.

In the meantime, the safest interim position, and this is engineering judgement rather than vendor guidance, is to take SOAP endpoints off the internet or restrict them with a firewall or VPN to the few systems that genuinely need them. Be aware that an attacker who can reach the endpoint does not need credentials, and service-level authentication does not help.

If a commercial supplier ships Axis 1 inside their product, ask them for a fixed release. If they have none, you are choosing between isolating the system and retiring it. CISA's catalogue entry advises discontinuing use of end-of-life products where mitigations are unavailable.

Check for signs of compromise

Do this for any affected system that was reachable from outside your network at any point since 6 November 2026, even if you have now patched it. Rapid7's published investigation of a Confluence intrusion began with unauthenticated POST requests to the SOAP endpoint. Within hours the attacker had moved on to the database, hunted for credentials and reached cloud and Microsoft 365 accounts, including a legacy-authentication sign-in roughly twelve hours after the first exploit request.

Review web server and application logs for unusual POST requests to the remote API endpoints, look for new processes or scheduled tasks on the server, and check identity logs for unfamiliar sign-ins, especially legacy authentication. Rapid7 has published network indicators for the Confluence and N-central attacks, which are worth searching your firewall and proxy logs for. Finding none does not prove you are clean, as Rapid7 itself cautions.

If you find anything suspicious, isolate the server from the network, keep it powered on where practical so evidence is preserved, rotate credentials the server could access and bring in incident-response support. In the UK, serious incidents may also need reporting to the ICO or NCSC depending on what was exposed.

Real-world reporting

Rapid7 states that its managed detection team observed exploitation against a customer's Confluence Data Center on 13 November 2026, and that N-able separately reported exploitation of N-central. A proof of concept targeting N-central appeared on 12 November. These are statements by Rapid7 and the vendors; CISA's catalogue entry confirms evidence of exploitation without identifying who was affected. We name no affected organisation here because none has been publicly identified in the sources we checked.

Update history

We’ll keep this page updated as new information becomes available. Check back for the latest developments.

  1. Initial advisory, 22 November 2026: CVE-2026-90436 was disclosed by Apache on 6 November 2026 and added to CISA's Known Exploited Vulnerabilities catalogue on 18 November 2026. No fixed Axis 1.x release is planned. Atlassian lists 9.2.28 as the Confluence Data Center fix and Rapid7 advises N-central 2026.4 HF3. Update source

Technical terms explained
end-of-life
Software its maintainers no longer develop or fix. Apache Axis 1 is in this state, so no patched release is planned.
Known Exploited Vulnerabilities
A list run by the US cyber agency CISA of vulnerabilities with credible evidence of exploitation in the wild. A listing does not identify who was attacked.
SOAP
An older XML-based way for programs to call services over a network. Many legacy business applications and some management tools still expose SOAP interfaces.
SOAP fault
The standard error message a SOAP service sends back when a request fails. This flaw is triggered by a specially crafted fault message.
unsafe reflection
A weakness where a program lets outside input decide which code class it loads or creates. Loading a class can run its startup code. It is catalogued as CWE-470.
XML-RPC
A simple older protocol for calling remote functions using XML over HTTP. Confluence's Remote API supports XML-RPC and SOAP.

Sources and further reading

KEEP THE CONVERSATION GOING

Not sure what is running Axis in your estate?

If you would like a second pair of eyes on an inventory of exposed Java systems, or help checking a server for signs of compromise, you are welcome to get in touch.

Contact Rismor