Exploitation / web applicationHighTLP:CLEAR

Axis CVE-2026-90436 Confluence

Attackers Exploit Apache Axis CVE-2026-90436 Against Confluence Data Center Servers With the SOAP API Enabled

Published
16 November 2026
Added
17 November 2026, 05:57 UK
Last updated
17 November 2026

1 to block now3 to hunt

Hunt3 platforms

Run the hunt before you block, to find past activity. The same hunt is published for each platform. Preview and copy the queries in the dashboard.

  • Defender XDRKQLDefender portal > Hunting > Advanced hunting. Paste and run over 30 days.Download hunt.kql
  • SplunkSPLSearch & Reporting, last 30 days or more. Reads the CIM data models.Download hunt.spl
  • Google SecOpsYARA-L 2.0Rules Editor. Paste, Retrohunt over 30 days, then turn on live mode.Download hunt.yaral

These queries can return false positives. Know your environment and confirm a hit before acting.

Summary

Rapid7 reported on 16 November 2026 that its MDR team saw CVE-2026-90436 exploited against an Atlassian Confluence Da... Apache will not ship a fixed Axis 1.x release, so other Java products that bundle Axis 1.x may also be exposed.

Do now

  1. Block the 1 indicator.
  2. Run the hunt.
  3. Upgrade Confluence Data Center now.

Indicators 4

ValueTypeActionCopy
192[.]238[.]253[.]176IPv4block
5[.]133[.]47[.]243IPv4alert
163[.]182[.]68[.]109IPv4alert
104[.]13[.]106[.]166IPv4alert

Sources Rapid7 · confluence.atlassian.com

More detail
Note Rapid7 is the single source for the Confluence source addresses and says their absence does not prove a server was untouched. 5[.]133[.]47[.]243 (Grain, UK broadband), 163[.]182[.]68[.]109 (Cincinnati Bell dynamic) and 104[.]13[.]106[.]166 (AT&T residential) are consumer or business broadband addresses and are alert only. The N-central addresses N-able listed (157[.]20[.]241[.]16, 139[.]99[.]69[.]109, 79[.]76[.]51[.]56) are already on the Able2Shell N-central page.

What to do

  1. Upgrade Confluence Data Center to 9.2.28 or a 10.x release, or clear Remote API (XML-RPC & SOAP) under General Configuration > Further Configuration; a request to /plugins/servlet/soap-axis1/confluenceservice-v2 should then return HTTP 403.
  2. Block 192[.]238[.]253[.]176 and search Confluence access logs, proxy and firewall logs from 6 November for all four Rapid7 addresses and for POST requests to /plugins/servlet/soap-axis1/ or /rpc/soap-axis/ paths.
  3. Hunt for java.exe or the Confluence service account spawning cmd.exe, powershell.exe, sh, bash, curl or wget, and for new JSP or class files under the Confluence install directory.
  4. Inventory other Java applications that bundle Apache Axis 1.x (axis.jar 1.4 or earlier) and follow each vendor's guidance.

Affected countries and sectors

Targets
Not stated
Sectors
Not stated

Background

Rapid7 reported on 16 November 2026 that its MDR team saw CVE-2026-90436 exploited against an Atlassian Confluence Data Center server in a customer environment on 13 November. The flaw is an unsafe reflection bug (CWE-470) in the end-of-life Apache Axis 1.x SOAP library, disclosed by Apache on 6 November and rated 9.8 by CISA, that gives an unauthenticated attacker remote code execution. Confluence Data Center 1.x to 9.x is exposed only when the Remote API (XML-RPC and SOAP) setting is on, which has been off by default for new installs since version 3.0; Atlassian fixed it in 9.2.28, and 10.x and Atlassian Cloud are not affected. N-able N-central with the Legacy API enabled uses the same library, and N-able reported exploitation that strongly correlates with this CVE on 13 November (covered on the Able2Shell N-central page). Apache will not ship a fixed Axis 1.x release, so other Java products that bundle Axis 1.x may also be exposed. Rapid7 published four source addresses seen exploiting Confluence; one is a hosting address and is on the block list, and three sit in residential or business broadband ranges and are alert only.

Downloads

View folder in repository

MITRE ATT&CK3

Open in the live dashboard Get the blocklist