Apache Axis CVE-2026-90436 Exploited: Confluence, N-central
TL;DR · the short version
CVE-2026-90436 is an unauthenticated remote code execution flaw in Apache Axis 1.x, an end-of-life Java SOAP library: Axis loads and instantiates a class named in an inbound SOAP fault before checking it, and the fault is handled before any per-service authentication. Apache disclosed it on 6 November 2026 with no fixed Axis 1.x release, only a patch and advice to migrate to Axis2. Atlassian says Confluence Data Center 1.x to 9.x with the Remote API (XML-RPC & SOAP) enabled are affected and fixed it in 9.2.28; Confluence 10.x and Cloud are not affected. Rapid7 says it detected exploitation against Confluence Data Center (responding on 13 November), and CISA added the CVE to KEV on 18 November with a due date of 21 November. For N-able N-central, a public exploit chain published on 12 November began with this Axis flaw where the non-default Legacy API was enabled; Previdian reported attempts and N-able published indicators of compromise, but N-able's notices do not name the CVE. N-central 2026.4 HF3 (2026.4.1.39, 16 November) permanently blocks the legacy APIs. Find Axis 1.x in your Java estate, patch Confluence and N-central, restrict SOAP endpoints and hunt for compromise.
Attackers are exploiting CVE-2026-90436, a critical flaw in the old Apache Axis 1.x Java library, against on-premises Atlassian Confluence Data Center, and an exploit chain against N-able N-central starts with it. Apache disclosed the flaw on 6 November 2026: an unauthenticated attacker can make Axis load and instantiate a Java class of their choosing, which can lead to remote code execution. Axis 1.x is end of life, so Apache will not ship a fixed 1.x release. Rapid7 says it detected exploitation against a Confluence Data Center server and responded on 13 November, and CISA added the CVE to its Known Exploited Vulnerabilities catalog on 18 November, with a due date of 21 November 2026. Atlassian's fix is Confluence 9.2.28; N-able's latest N-central build is 2026.4 HF3 (2026.4.1.39).
Who this is for: CISOs, vulnerability-management and application owners, and anyone who runs Confluence Data Center, N-central or other Java software that may bundle Axis 1.x.
Based on the CVE record, Apache's oss-security notice, the CISA KEV catalog, Atlassian's and N-able's advisories and release notes, Rapid7's analysis and Field Effect's summary, read on 19 November 2026. PlayCISO is not affiliated with Apache, Atlassian, N-able, Rapid7 or Field Effect. We publish no exploit details.
Confirmed vs not yet known
Apache confirms (CVE record and oss-security, 6 Nov 2026): all Apache Axis 1.x versions through 1.4 are affected (CWE-470, unsafe reflection); the inbound SOAP fault is parsed before any per-service handler chain runs, so service-level authentication does not protect against it; the project "does not expect to create an Axis 1.x release fixing this problem" and recommends Axis2/Java or a build with its patch applied.
CISA confirms exploitation: in KEV, date added 18 November 2026, due 21 November 2026, forensic triage required "Yes", known ransomware use "Unknown". CISA's enrichment of the CVE record scores it CVSS 3.1 9.8 with "Exploitation: active" and "Automatable: yes".
Atlassian confirms: Confluence Data Center 1.x to 9.x are affected when the Remote API (XML-RPC & SOAP) is enabled (CVSS 4.0 9.3, its own assessment); fixed in 9.2.28; Confluence 10.x and Cloud are not affected. Atlassian's advisory does not say whether the flaw is exploited.
Rapid7 reports: its managed detection team detected exploitation against Confluence Data Center in a customer environment and responded on 13 November. Rapid7 says N-able reported in-the-wild exploitation of N-central "for a vulnerability that strongly correlates" with this CVE.
N-able says: the N-central server issue disclosed on 12 November depends on the non-default Legacy API being turned on and exposed to the internet, and it has "identified Indicators of Compromise (IOCs) relevant only to customers who have not disabled the Legacy API". N-able's notices we read do not name CVE-2026-90436 or Apache Axis.
Not yet known: who is behind the attacks (Rapid7 names no actor), how many servers were compromised, and which other products bundle Axis 1.x. Field Effect lists Confluence Data Center and N-central as the products confirmed affected as of 17 November and says exposure likely extends further. NVD had not completed its own analysis when we checked.
Affected and fixed versions
| Product | Affected | Fixed or mitigated | Source |
|---|---|---|---|
| Apache Axis 1.x (axis:axis, org.apache.axis:axis) | All versions through 1.4 (end of life) | No fixed release. Migrate to a different SOAP engine such as Apache Axis2/Java, or use a build with Apache's patch applied | CVE record, oss-security |
| Debian axis packages | bookworm, trixie, forky and sid listed vulnerable | Unfixed when checked on 19 Nov | Debian tracker |
| Atlassian Confluence Data Center | 1.x to 9.x with "Remote API (XML-RPC & SOAP)" enabled | 9.2.28, or a current 10.x release (10.x removed the feature). Workaround: turn off the Remote API | Atlassian |
| Atlassian Cloud (atlassian.net) | Not affected | No action | Atlassian |
| N-able N-central (on-premises) | Rapid7: 2026.4 HF2 when the Legacy API is enabled. N-able gives no affected range for this CVE | 2026.4 HF3 (2026.4.1.39), which permanently blocks the legacy APIs; upgrade all agents and probes too. Until then, confirm the Legacy API is disabled | N-able, Rapid7 |
| N-able N-central (hosted) | N-able says hosted environments were not affected by the Legacy API issue | N-able upgrades the server; customers upgrade agents and probes to HF3 | N-able, HF3 notes |
Atlassian says the Remote API has been off by default for new Confluence installations since version 3.0, so the question for each server is whether someone turned it on, usually for an old integration. Atlassian suggests confirming the workaround by requesting the Axis SOAP service path under /plugins/servlet/ on your own server: a correct mitigation returns HTTP 403. Turning the Remote API off may break scripts and add-ons that use it, so test first.
HF3 also fixes 17 other N-central CVEs (CVE-2026-129271 to CVE-2026-129287) from a run of public zero-day disclosures in November. N-able says agents and probes that are not upgraded "are susceptible to impersonation".
What the attackers did, at a defender's level
All of this is Rapid7's account of one Confluence intrusion its managed detection team handled. We give no commands or indicators here; Rapid7's post has them for defenders.
- Code ran as the Confluence service account. The Confluence Java process started shell and download commands, fetching hundreds of commands from short-lived tunnelling services.
- Fast, broad collection. The attacker enumerated the host, network, configuration, encryption keys and database settings, then within about three minutes queried the Confluence database and searched pages and attachments for credentials, tokens, VPN configurations, private keys and payment card numbers.
- Identity next. They queried the Atlassian Crowd API for users and groups and attempted AS-REP roasting against a domain controller; Rapid7 says those attempts failed.
- Then the cloud. About four hours after the first exploit request, a service-account credential was used to query a production cloud data warehouse; about twelve hours in, the attacker signed in to Microsoft 365 as an integration service account using legacy authentication.
- Possibly AI-assisted. Rapid7 says the commands and scripts appear "likely AI-generated" and their structure "suggests the use of AI-assisted automated tooling". It names no threat actor.
The lesson is the speed: a wiki server held secrets that reached the data warehouse and Microsoft 365 within hours. Treat any Confluence or N-central server that was exposed with the vulnerable API enabled after 6 November as possibly compromised until checked.
Useful next, if this was relevant to you
N-central: what is and is not established
On 12 November a researcher published zero-day exploits for N-central, including one The Hacker News calls 4EverAble2Shell, as part of a series of public disclosures. The Hacker News reported that Previdian saw targeted probing within hours, in a chain that attempted initial code execution through the Axis flaw and then tried to escalate to root, and that there was no evidence of successful exploitation at that point. N-able says the server issue needs the non-default Legacy API enabled and exposed to the internet, and on 13 November said it had identified indicators of compromise relevant only to customers who had not disabled the Legacy API. Rapid7 says N-able reported exploitation in the wild of a vulnerability that "strongly correlates" with CVE-2026-90436. N-able's own pages we read name other CVEs, not this one. N-central has appeared in CISA's KEV catalog several times in 2026; see N-able in the Breach Index.
Timeline
| Date | Event | Source |
|---|---|---|
| 11 Sep 2026 | Apache reserves CVE-2026-90436 | CVE record |
| 6 Nov 2026 | Apache Axis publishes the CVE and oss-security notice: all Axis 1.x through 1.4, no 1.x release expected, patch commit and Axis2 advised; credits José Apari-Pantigozo (OKIOK) | oss-security, Apache list |
| 9 Nov 2026 (22:00 PST) | Atlassian advisory: Confluence Data Center 1.x to 9.x with Remote API enabled, fixed in 9.2.28; Cloud and 10.x not affected | Atlassian |
| 12 Nov 2026 | Public exploits for N-central published; N-able says the server issue needs the non-default Legacy API enabled and exposed; Previdian reports attempts starting with the Axis flaw, no evidence of success at the time | The Hacker News, N-able |
| 13 Nov 2026 | Rapid7 MDR responds to exploitation of Confluence Data Center in a customer environment; N-able says it has IOCs relevant to customers who had not disabled the Legacy API | Rapid7, N-able |
| 16 Nov 2026 | Rapid7 publishes; N-able releases N-central 2026.4 HF3 (2026.4.1.39), permanently blocking legacy APIs | Rapid7, N-able |
| 17 Nov 2026 | CISA's CVE enrichment sets "Exploitation: active"; Rapid7 says a Metasploit module for Confluence was released | CVE record, Rapid7 |
| 18 Nov 2026 | CISA adds CVE-2026-90436 to KEV, due 21 November; Field Effect summarises Confluence and N-central as confirmed affected | CISA KEV, Field Effect |
What security leaders should do this week
- Find Axis 1.x across your Java estate. Search servers, application folders and container images for
axis.jarandaxis-1.4.jar; check Maven and Gradle dependency trees and supplier SBOMs foraxis:axisandorg.apache.axis:axis; look inweb.xmlfiles forAxisServlet; and check web logs for requests to/services/or/axis/services/paths and tohappyaxis.jsp. Commercial Java products often bundle Axis without saying so: ask your vendors in writing whether theirs does and when they will ship a fix. - Patch Confluence and N-central first. Confluence Data Center to 9.2.28 or a current 10.x; if you cannot this week, turn off the Remote API (XML-RPC & SOAP) and confirm the check returns 403. N-central to 2026.4 HF3 (2026.4.1.39) with every agent and probe upgraded; until then, confirm the Legacy API is disabled. Federal agencies have until 21 November under KEV; the BOD 26-04 calculator shows the clock.
- Block SOAP endpoints at the edge where they are not needed. No Axis-based service should be reachable from the internet unless a named integration needs it; restrict the rest to known source systems. Axis itself will never get a 1.x fix, so for anything you cannot upgrade, network restriction is the lasting control.
- Hunt on anything that was exposed after 6 November. Look for unusual SOAP POST requests, Java service processes starting shells, download tools or scripts, new web shells, scheduled tasks or services, and unexpected outbound connections, as Field Effect advises. Review what secrets the server could read (database passwords, API tokens, service accounts, cloud keys) and check those accounts' sign-ins, especially legacy authentication to Microsoft 365. CISA's KEV entry sets forensic triage to "Yes".
- If you find compromise, rebuild the server rather than clean it, rotate application and service-account credentials and any secrets stored in Confluence pages or attachments, and review authentication across connected identity, cloud and management platforms. Run the response through the IR Playbook Lab if your team has not practised this kind of incident.
- Record the end-of-life risk. Put every remaining Axis 1.x dependency in your risk register with an owner and a migration date, and rank it with the vulnerability prioritizer.
Why an old library keeps coming back
Axis 1.x has long been superseded by Axis2 and is end of life, yet it still sits inside enterprise products that expose SOAP APIs. When a flaw lands in an end-of-life component, the project cannot fix it for you and the products that bundle it decide on their own schedules. This is a software bill of materials problem as much as a patching one: the organisations that knew where Axis lived could act on 6 November, and the rest learned from exploitation reports. The same applies to the Java runtime itself; see our write-up on Java4Shell (CVE-2026-114938).
CISA added this CVE to KEV in the same batch as flaws in Synology DSM, LiteLLM and REDCap; see our round-up of the 18 November KEV additions. A day earlier Apache disclosed another exploited Java flaw, in the Roller blog server: Apache Roller CVE-2026-129448.
None of this is a breach of Apache, Atlassian or N-able. See Apache, Atlassian and N-able in the Breach Index.
Frequently asked questions
What is CVE-2026-90436?
A critical flaw in Apache Axis 1.x, an old Java library for SOAP web services. Per the CVE record Apache published on 6 November 2026, when an inbound SOAP fault names a Java class, Axis loads that class and may create an instance of it before checking that it is a legitimate fault type. With a suitable class on the application's classpath this leads to remote code execution, without a login: the fault is handled before any per-service authentication runs. It is classed CWE-470 (unsafe reflection). CISA scores it CVSS 3.1 9.8.
Is CVE-2026-90436 being exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 18 November 2026 with a due date of 21 November 2026. Rapid7 says its managed detection team detected exploitation against an Atlassian Confluence Data Center server in a customer environment and responded on 13 November. For N-able N-central, Rapid7 says N-able reported in-the-wild exploitation of a vulnerability that "strongly correlates" with this CVE, and The Hacker News reported Previdian's finding of attempts that started with this Axis flaw, with no evidence of success at the time. N-able's own notices do not name the CVE.
Is there a fixed version of Apache Axis 1.x?
No. Axis 1.x is end of life, the CVE is marked "unsupported when assigned", and the Apache Axis project says it does not expect to release an Axis 1.x version fixing it. Apache recommends moving to a different SOAP engine such as Apache Axis2/Java, or using an Axis build with its published patch applied. Debian lists its axis packages as vulnerable with no fix.
Which Confluence versions are affected by CVE-2026-90436?
Atlassian says Confluence Data Center 1.x through 9.x are affected when the "Remote API (XML-RPC & SOAP)" setting is enabled, and lists 9.2.28 as the fixed version. Confluence 10.x removed the feature and is not affected, and Atlassian Cloud sites are not affected. The Remote API has been off by default for new installations since Confluence 3.0, so check whether yours was turned on.
Which N-central versions are affected?
N-able does not tie its fixes to CVE-2026-90436. It says the server issue disclosed on 12 November depends on a non-default configuration in which the Legacy API is turned on and exposed to the internet. Rapid7 says N-central 2026.4 HF2 is affected when the Legacy API is enabled. N-central 2026.4 HF3 (2026.4.1.39), released 16 November 2026, permanently blocks the legacy APIs and fixes 17 further CVEs. On-premises customers must upgrade the server and all agents and probes; for hosted N-central, N-able upgrades the server and customers upgrade agents and probes.
How do I find Apache Axis 1.x in my environment?
Search servers, application directories and container images for axis.jar or axis-1.4.jar, check Maven and Gradle dependency trees and supplier SBOMs for axis:axis or org.apache.axis:axis, look in web.xml files for AxisServlet, and check web logs for requests to /services/ or /axis/services/ paths and for happyaxis.jsp. Many commercial Java products bundle Axis without listing it, so ask your vendors directly.
What should I do if I cannot patch Confluence or N-central yet?
For Confluence, Atlassian's workaround is to turn off "Remote API (XML-RPC & SOAP)" under General Configuration, Further Configuration (no restart needed); it may break scripts and add-ons that use the API, so test first. For N-central, confirm the Legacy API is disabled using N-able's instructions. For any other product, block or restrict the SOAP endpoints at the network edge so only known systems can reach them. Then look for signs of compromise, because exploitation started before many organisations knew.
Was Atlassian or N-able hacked?
No breach of Atlassian's or N-able's own systems is reported in the sources we read. CVE-2026-90436 is a vulnerability in an open-source library their on-premises products used. The exposure is to organisations running an affected Confluence Data Center or N-central server.
Sources
- CVE.org: CVE-2026-90436 (CNA Apache Software Foundation; CISA ADP CVSS 3.1 9.8 and SSVC)
- Apache Axis: CVE-2026-90436 notice on oss-security (6 November 2026) and the Apache mailing-list thread
- Apache Axis 1.x patch commit (GitHub)
- CISA Known Exploited Vulnerabilities catalog: CVE-2026-90436 (added 18 November 2026, due 21 November 2026)
- Atlassian: CVE-2026-90436, Remote Code Execution in Confluence Data Center (9 November 2026) and Confluence 9.2.28 release notes
- N-able: N-central 2026.4 HF3 release notes (16 November 2026)
- N-able: N-able Vulnerability Remediation Update (13 November 2026, updated 16 November) and New Security Update on N-central (13 November 2026)
- NVD: CVE-2026-90436
- Debian security tracker: CVE-2026-90436
- Rapid7: exploitation of CVE-2026-90436 against Confluence Data Center (16 November 2026, updated 19 November)
- The Hacker News: new N-central exploits (12 November 2026; Previdian's report of attempts)
- Field Effect: Apache Axis exploitation highlights legacy component risks (18 November 2026)