# Apache Axis flaw CVE-2026-90436 is now exploited in Confluence Data Center and N-central. What to do

> Rapid7 says attackers hit a Confluence Data Center server through an unauthenticated bug in the long-dead Apache Axis 1.x SOAP library on November 13, the same day N-central servers were compromised through it. If you run Confluence 9.x or older with its Remote API on, patch to 9.2.28 or switch the API off now.

Published Nov 16, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/apache-axis-cve-2026-90436-exploited-confluence-data-center-n-central-what-to-do

**Attackers are exploiting CVE-2026-90436, an unauthenticated remote code execution bug in the Apache Axis 1.x SOAP library, against Atlassian Confluence Data Center**, Rapid7 said on November 16. Its managed detection team saw the attack in a customer environment on **November 13**, the same day N-able reported attacks on its N-central remote-management servers through what Rapid7 calls a strongly correlated flaw.

Why it matters: Axis 1.x is end-of-life and is bundled inside other vendors' products. Apache does not plan a fixed 1.x release, so a fix depends on each product vendor. Two products are now confirmed as exploited. Both are vulnerable only in a non-default setup, but Confluence's Remote API is common on servers that run scripts and integrations.

## What the bug is

Rapid7 describes CVE-2026-90436 as unsafe reflection (CWE-470) in Axis 1.x through 1.4. The Hacker News says it is abused through unsafe class instantiation when Axis processes a SOAP fault. No login is needed. Severity scores differ by source:

| Source | Score |
|---|---|
| CISA (per Rapid7) | 9.8 critical |
| Atlassian (CVSS 4.0, its own assessment) | 9.3 critical |

## Timeline

| Date (2026) | Event | Source |
|---|---|---|
| Nov 6 | Apache discloses the Axis flaw | Rapid7 |
| Nov 9 | Atlassian publishes its Confluence Data Center advisory | Atlassian |
| Nov 12 | Researcher Sean Bales publishes "4EverAble2Shell", an N-central exploit chain that uses the Axis bug for entry; full exploit attempts begin at 09:16 UTC | BleepingComputer |
| Nov 13 | Rapid7 sees exploitation of Confluence Data Center; N-able reports N-central exploitation | Rapid7 |
| Nov 16 | Rapid7 publishes its alert; N-able finishes upgrades of hosted N-central | Rapid7, The Hacker News |

Atlassian's advisory does not say whether the flaw is being exploited, and Atlassian says it cannot tell whether your instance was hit. Rapid7's alert is the first public report of attacks on Confluence that we found.

## Who is affected

- **Confluence Data Center 1.x through 9.x**, but only if **Remote API (XML-RPC & SOAP)** is enabled. Atlassian says Confluence 10.0 removed the feature, so 10.x and later are not affected. **Atlassian Cloud** sites on atlassian.net or jira.com are not affected.
- **N-able N-central** with the **Legacy API** enabled. BleepingComputer says the Legacy API is off by default, but Huntback found at least **21 compromised production N-central servers**, **19 of them on the latest Hotfix 2** (2026.4.1.26). Attackers chained the Axis bug with a separate N-central privilege-escalation weakness to reach root and install crypto miners.
- **Anything else that bundles Axis 1.x.** Rapid7 names only these two products as exploited. If you run older Java software with SOAP endpoints, ask the vendor whether it ships Axis 1.x.

## What to do: Confluence Data Center

1. **Upgrade to 9.2.28**, or to a current 10.x release, which drops the vulnerable API (Atlassian, Rapid7).
2. **If you can't patch today, turn the Remote API off.** As an admin, go to the gear menu, then **General Configuration**, then **Further Configuration**. Click **Edit**, clear **Remote API (XML-RPC & SOAP)** and save. No restart is needed, but scripts and add-ons that use the API may break.
3. **Check that it worked.** Browse to this path on your server:

```
<base_url>/plugins/servlet/soap-axis1/confluenceservice-v2
```

Atlassian says you should get **HTTP 403 Forbidden**. A page that mentions "confluenceservice-v2" or an "AXIS service" means the API is still reachable.

4. **Hunt for compromise** on any server that was internet-facing with the API on. Rapid7 lists these Confluence-related IPs: `192.238.253[.]176`, `5.133.47[.]243`, `163.182.68[.]109`, `104.13.106[.]166`. It warns that finding none does not prove you are clean.

## What to do: N-central

**Update, November 18:** N-able released **N-central 2026.4 Hotfix 3** on Monday, November 16, SecurityWeek reports. It fixes **17 vulnerabilities, CVE-2026-129271 through CVE-2026-129287**, covering privilege escalation, predictable passcodes, missing authentication, XXE, SSRF and remote code execution. HF3 also removes the setting that let admins turn the Legacy API back on, so the API is now permanently blocked, which shuts off the 4EverAble2Shell chain. SecurityWeek says hosted environments are already patched. It does not say which of the 17 CVEs were exploited.

1. **Upgrade on-premises servers to 2026.4 HF3 now.** Until you do, confirm the Legacy API is disabled, including on servers running HF2.
2. **Upgrade all Agents and Probes.** SecurityWeek says HF3 adds stronger Agent verification, and Agents and Probes that are not upgraded can be impersonated. Hosted customers need to do this too.
3. **Look for signs of compromise.** BleepingComputer lists these signs:
   - requests to `/dms/services/ServerUI` that mention `jline.internal.TerminalLineSettings`
   - an unexpected `xvd.service` systemd unit
   - mining processes
   - files in `/tmp/.xvd` or `/var/tmp/.xvd`
   - traffic to `157.20.241[.]16`

   Rapid7 adds `139.99.69[.]109` and `79.76.51[.]56`.
4. **Treat any hit as full server compromise**, because the chain ends in root. Huntback says applying HF2 alone is not enough.

For background on the earlier N-central disclosures and shutdown, see [our Able2Shell guide](/security/n-able-n-central-offline-able2shell-33-zero-days-poc-what-msps-should-do).

## What to watch

- **Update, November 19:** CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities list on November 18, with a November 21 deadline for federal agencies, according to SecurityOnline. See [our KEV guide](/security/cisa-kev-litellm-redcap-synology-apache-axis-three-day-deadline-what-to-patch).
- Whether more vendors that bundle Axis 1.x issue advisories.
- Whether N-able says which of the 17 HF3 flaws were exploited in the wild.


## Sources

1. [Rapid7 — Rapid7 detected exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also exploited](https://www.rapid7.com/blog/post/etr-rapid7-detected-exploitation-of-cve-2026-90436-against-atlassian-confluence-data-center-n-able-n-central-also-exploited/)
2. [Atlassian — CVE-2026-90436: Remote code execution in Confluence Data Center](https://confluence.atlassian.com/security/cve-2026-90436-remote-code-execution-in-confluence-data-center-1874560038.html)
3. [BleepingComputer — New N-able '4EverAble2Shell' zero-day exploited hours after PoC released](https://bleepingcomputer.com/news/security/new-n-able-4everable2shell-zero-day-exploited-hours-after-poc-released)
4. [The Hacker News — Hackers exploit N-central flaws to infect 21 servers, including 19 running Hotfix 2](https://thehackernews.com/2026/11/hackers-exploit-n-central-flaws-to.html)
5. [SecurityWeek — N-able kills legacy APIs, patches 17 N-central zero-days](https://www.securityweek.com/n-able-kills-legacy-apis-patches-17-n-central-zero-days/)
6. [SecurityOnline — CISA Adds 4 Exploited Flaws to KEV: Synology DSM, LiteLLM](https://securityonline.info/cisa-adds-4-exploited-flaws-kev-synology-litellm/)
