Confluence Data Center RCE CVE-2026-90436 Is Exploited: Affected Versions, Fix 9.2.28 and the Workaround

Published:

Attackers are exploiting CVE-2026-90436, a critical remote code execution flaw in Apache Axis 1.x that affects Confluence Data Center when its Remote API is switched on. Rapid7 says its managed detection team saw exploitation against Confluence Data Center in a customer environment on November 13, 2026, and published its findings on November 16. Atlassian’s fix is Confluence Data Center 9.2.28, and there is a no-restart workaround for teams that cannot patch today. Here is who is affected, how to check, and what is still unknown.

What is CVE-2026-90436?

CVE-2026-90436 is an unsafe reflection flaw (CWE-470) in Apache Axis 1.x, an old Java web-services library that Confluence uses for its XML-RPC and SOAP APIs. Apache disclosed it on November 6, 2026. It lets an unauthenticated attacker run code on the server. Atlassian’s security advisory, released on November 9, rates it critical at 9.3 on the CVSS 4.0 scale; Rapid7 cites a score of 9.8. Axis 1.4 and earlier are end of life, and Rapid7 reports there is no planned fixed Axis 1.x release, which is why vendors are patching their own products instead.

Which Confluence versions are affected?

  • Confluence Data Center 1.x through 9.x: affected, but only when the “Remote API (XML-RPC & SOAP)” setting is enabled. Atlassian says that setting has been off by default for new installations since Confluence 3.0, so older sites that kept it on, or turned it on for an integration, are the ones at risk.
  • Confluence 10.x and above: not affected. Version 10.0 removed the feature.
  • Atlassian Cloud: not affected, and Atlassian says no action is needed.

The fixed release in Atlassian’s table is 9.2.28. Atlassian also advises moving to the latest version, and notes that its policy no longer includes binary patches. Because the advisory’s affected range and fixed-version table do not line up perfectly for every branch, check the release notes for your branch before you schedule the upgrade.

Is CVE-2026-90436 being exploited?

Yes, according to Rapid7. Its timeline: a proof-of-concept exploit aimed at N-able N-central was published on November 12; on November 13 Rapid7’s MDR team detected exploitation against Confluence Data Center in a customer environment; and Rapid7 published on November 16, updating the page on November 17. Rapid7 recommends emergency remediation outside normal patch cycles, starting with internet-facing systems. Atlassian’s own advisory does not state that exploitation has occurred and says it “cannot confirm if your instances have been affected,” so treat the in-the-wild claim as Rapid7’s finding.

The same Axis flaw is also being used against N-able N-central through its Legacy API. Rapid7 says N-able released N-central 2026.4 HF3 (2026.4.1.39), which disables Legacy API, and that on-premises admins should confirm Legacy API is off even on 2026.4 HF2.

As of November 17, sources we checked did not show the flaw in CISA’s Known Exploited Vulnerabilities catalog. For what has been added recently, see our Exploited This Week list, the UnrealIRCd and Check Point write-ups.

How do you fix it or work around it?

  1. Upgrade to Confluence Data Center 9.2.28 or an unaffected 10.x release.
  2. If you cannot patch yet: sign in as an administrator, open General Configuration, then Further Configuration (<base_url>/admin/viewspacesconfig.action), click Edit, clear “Remote API (XML-RPC & SOAP)” and save. No restart is needed. Atlassian warns this can break scripts, automations and third-party add-ons that use the remote API, so test it first.
  3. Check the workaround worked: browse to <base_url>/plugins/servlet/soap-axis1/confluenceservice-v2. A “HTTP Status 403 – Forbidden” page means it is working. Any message mentioning “confluenceservice-v2” or “AXIS service” means recheck the setting or contact Atlassian support.
  4. Hunt for compromise. Rapid7 lists these Confluence-related IP addresses: 192.238.253[.]176, 5.133.47[.]243, 163.182.68[.]109 and 104.13.106[.]166. Finding them in logs warrants investigation; not finding them does not prove a system is clean.

How many Confluence servers are exposed?

Censys counted 1,212,568 internet-facing Confluence web properties in a November 16 advisory, as reported by Cyber Security News. That number is hostname-and-port pairs where Confluence was detected. It does not show how many are Data Center, which versions they run, or whether the Remote API is on, so it is not a count of vulnerable servers.

What is still unknown

  • What attackers do after they gain code execution on Confluence. Rapid7 confirms exploitation but does not describe follow-on activity, and nothing in the sources links this to ransomware.
  • How many Confluence Data Center customers have been hit. No figure has been published.
  • Whether CISA will add the flaw to its KEV list, which would set a federal patch deadline.

The practical takeaway for IT teams: if you run Confluence Data Center, find out whether the Remote API is enabled today. If it is, patch or switch it off first, then investigate.

Sources: Atlassian security advisory CVE-2026-90436 (Nov 9, modified Nov 10, 2026); Rapid7, Nov 16, updated Nov 17, 2026; Cyber Security News, Nov 17, 2026.

Like our coverage? Add stepphase.com as a preferred source on Google to see more of our stories in Top Stories.

Saif Ali Tai
Saif Ali Taihttps://xplorely.com/
I'm Saif Ali Tai, a tech blogger and software engineer with 8+ years of experience building apps, and I run StepPhase as its editor. I cover technology news, AI tools and security stories that matter to everyday users. Articles here are drafted with AI assistance and checked against the sources linked in each post.

Related articles

Recent articles