What is Apache Axis?
Apache Axis 1.x is a Java implementation of SOAP, the XML-based remote procedure call protocol that dominated enterprise web services in the 2000s. An application embeds Axis to expose Java methods as SOAP services over HTTP and to act as a client against other SOAP endpoints. Axis 1.4, the final release, shipped in 2006. The project reached end of life long ago and the Apache Axis team explicitly does not plan to publish any further 1.x release.
Dead code does not stop running. Axis 1.x survives as a bundled dependency deep inside commercial Java products that still offer legacy XML-RPC and SOAP interfaces for backward compatibility, and those products are often the administrative hub of an environment: a wiki holding the company's internal documentation, or a remote monitoring and management platform with agents on every endpoint. A flaw in an abandoned library therefore lands as a flaw in supported, patched, actively used software whose owners may not know Axis is in the build at all.
Overview
CVE-2026-90436 is an unsafe reflection flaw in how Axis 1.x deserializes an inbound SOAP fault. When a fault contains a <detail><exceptionName> element, Axis loads the class that element names. If a <data> element is present as well, Axis instantiates that class through its String constructor. Merely loading the class is already enough to run its static initializer. With a suitable gadget class on the application's classpath, this becomes unauthenticated remote code execution.
The detail that turns an awkward primitive into a critical, pre-authentication bug is ordering: the fault is parsed before the per-service handler chain runs. Any authentication handler configured on the service never gets the chance to reject the request. CISA scores the issue 9.8 under CVSS v3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); Apache rates it Critical and tagged the CVE record UNSUPPORTED WHEN ASSIGNED.
Apache disclosed the flaw on oss-security on 2026-11-06. Exploitation followed within a week: a proof of concept appeared on 2026-11-12, and on 2026-11-13 Rapid7's managed detection team caught it being used against a customer's Atlassian Confluence Data Center server while N-able reported attacks against N-central the same day. CISA added the CVE to the KEV catalog on 2026-11-18 with a BOD 26-04 deadline of 2026-11-21.
Affected Versions
| Product | Vulnerable | Fixed |
|---|---|---|
| Apache Axis 1.x (EOL) | 1.x through 1.4, commits aac718c6 through 41f3b4e8 | No release planned; apply commit 41f3b4e8 or migrate to Axis2/Java |
| Atlassian Confluence Data Center and Server | 1.x through 9.x with Remote API (XML-RPC and SOAP) enabled | 9.2.28, or 10.x (feature removed) |
| N-able N-central | Releases with the Legacy API feature enabled | 2026.4 HF3 (2026.4.1.39), which disables it |
Debian bookworm axis package |
Vulnerable | No fix at the time of writing |
Both Confluence and N-central require a non-default configuration to be reachable: Remote API on Confluence and Legacy API on N-central are off unless an administrator or an older integration turned them on. Atlassian Cloud is not affected. Any other Java product embedding Axis 1.x should be treated as a candidate until proven otherwise.
Technical Details
The CWE is CWE-470, unsafe reflection: the program lets untrusted input choose which class it loads and instantiates. Java's Class.forName runs the target class's static initializer as a side effect of loading, so the attacker does not even need the constructor path to get code running, though the String constructor gives a second and more controllable route. What an attacker can achieve therefore depends on what is on the victim application's classpath, which is why a sprawling product like Confluence, with hundreds of bundled libraries, is a far better target than a minimal Axis deployment.
The attack is a single unauthenticated HTTP POST carrying a crafted SOAP fault to any endpoint handled by Axis. No prior access, no user interaction, no chaining with a second vulnerability, and no memory corruption or timing dependence. In Rapid7's observed incident the requests returned HTTP 500 errors, which makes a 500 on a SOAP path a useful hunting signal rather than evidence that the attack failed.
Apache's fix, commit 41f3b4e8 in the axis-axis1-java repository, moves the fault-type check ahead of the class load so that an arbitrary exceptionName is no longer resolved. Because there will be no Axis 1.x release, consumers must either rebuild Axis with that commit applied or move off the engine entirely.
Discovery
The vulnerability was found and reported by Jose Apari-Pantigozo of OKIOK. Robert Lazarski posted the Apache Axis project's announcement to the oss-security mailing list on 2026-11-06 at 15:32 UTC, crediting the finder and publishing the patch commit at the same time. Downstream vendors were left to work out their own exposure: Atlassian's Confluence advisory and N-able's N-central hotfix both followed the Apache disclosure rather than preceding it, which is the usual pattern when an end-of-life library is patched in the open.
Rapid7's Managed Detection and Response team detected the first publicly reported in-the-wild exploitation and published its analysis, with indicators, on 2026-11-16.
Exploitation Context
Rapid7 observed the full intrusion chain against Confluence Data Center on 2026-11-13. Unauthenticated POST requests hit a SOAP endpoint, and within seconds the Confluence Java process spawned Bash and curl. The intruder enumerated the host and the database, pulled attachments and credentials, attempted an AS-REP roasting attack against Active Directory, and roughly 12 hours after the first request signed in to the victim's Microsoft 365 tenant from 192.238.253.176. Rapid7 noted characteristics suggesting AI-assisted tooling in the hands-on-keyboard phase.
Rapid7 published these indicators for the Confluence activity: 192.238.253.176, 5.133.47.243, 163.182.68.109, 104.13.106.166, subdomains of trycloudflare.com, wpefh-192-238-253-176.free.pinggy.net, and webhook.site. For N-central: 157.20.241.16, 139.99.69.109, and 79.76.51.56. Their absence does not clear an environment.
No reliable count of internet-exposed vulnerable instances has been published. CISA has not named a threat actor and the KEV entry does not record known ransomware use, but the post-exploitation behavior Rapid7 described, credential theft followed by pivoting into cloud identity, is consistent with either an access broker or an early ransomware intrusion stage.
Remediation
- Upgrade Confluence Data Center and Server to 9.2.28, or to a current 10.x release where the Remote API has been removed entirely.
- Upgrade N-able N-central to 2026.4 HF3 (2026.4.1.39) on an emergency basis and confirm that the Legacy API feature is disabled afterward.
- If patching has to wait, disable the Remote API (XML-RPC and SOAP) in Confluence administration, and disable the Legacy API in N-central. This is the only effective workaround and it will break integrations that still rely on those interfaces.
- For your own Java applications, search the build for Axis 1.x. Migrate to Apache Axis2/Java, or rebuild Axis with commit 41f3b4e8 applied. There will be no official 1.x release, so an unmodified Axis 1.4 jar stays vulnerable forever.
- Block external access to SOAP endpoints at the network edge and restrict them to known integration hosts. Per-service authentication handlers do not stop this request, so authentication is not a mitigation here.
- Hunt in logs: unauthenticated POST requests to SOAP paths returning HTTP 500, any child process of the application's Java process (bash, sh, curl, wget, cmd.exe), outbound connections to the Rapid7 indicators above, and new or unexpected Kerberos AS-REQ activity from the application server.
- If exploitation is confirmed, rotate every credential the application could reach, including database credentials, integration tokens, and any cloud or directory identity it holds, and review authentication logs for the following days. The observed intrusion reached Microsoft 365 within half a day.
- Federal civilian agencies must remediate by 2026-11-21 under BOD 26-04 and follow the accompanying Forensics Triage Requirements, or discontinue use of the product.
Key Details
| Property | Value |
|---|---|
| CVE ID | CVE-2026-90436 |
| Vendor / Product | Apache - Axis |
| NVD Published | 2026-11-06 |
| NVD Last Modified | 2026-11-18 |
| CVSS 3.1 Score | 9.8 |
| CVSS 3.1 Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Severity | CRITICAL |
| CWE | CWE-470 find similar ↗ |
| CISA KEV Added | 2026-11-18 |
| CISA KEV Deadline | 2026-11-21 |
| Known Ransomware Use | No |
CVSS 3.1 Breakdown
Required Action
Timeline
| Date | Event |
|---|---|
| 2026-11-06 | Apache discloses CVE-2026-90436 on oss-security; CVE published |
| 2026-11-12 | Proof-of-concept exploit targeting N-able N-central published |
| 2026-11-13 | Rapid7 MDR detects exploitation against Confluence Data Center; N-able reports exploitation of N-central |
| 2026-11-16 | N-able releases N-central 2026.4 HF3 |
| 2026-11-18 | Added to CISA Known Exploited Vulnerabilities catalog |
| 2026-11-21 | CISA BOD 26-04 remediation deadline |
References
| Resource | Type |
|---|---|
| NVD - CVE-2026-90436 | Vulnerability Database |
| CISA KEV Catalog Entry | US Government |
| Apache announcement - CVE-2026-90436: Apache Axis 1.x (EOL): unauthenticated remote class instantiation via SOAP fault exceptionName | Vendor Advisory |
| Apache Axis - patch commit 41f3b4e8 | Vendor Advisory |
| Rapid7 - Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited | Security Research |
| SecurityOnline - Confluence Data Center RCE CVE-2026-90436 Actively Exploited | News |
| CISA Alert - CISA Adds Four Known Exploited Vulnerabilities to Catalog | US Government |