Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsVulnerability Advisory

Confluence Data Center Exploitation: CVE-2026-90436 Patch Steps

CVE-2026-90436 exploitation hit Confluence Data Center with Remote API enabled. Check exposure, update to 9.2.28, and investigate affected hosts.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
17 November 2026
Reading time
4 min read
Abstract server and API gate illustrating a Confluence patch and configuration response.

CVE-2026-90436 exploitation is now a confirmed Confluence Data Center response issue: Rapid7 MDR says it detected an attempt in a customer environment on 13 November 2026. Atlassian says exposure requires the Remote API (XML-RPC & SOAP) setting to be enabled. Administrators can use a vulnerability intelligence platform to prioritize affected installations, then apply Atlassian’s fixed 9.2.28 release or a current unaffected 10.x release.

Advisory
Severity Critical
Confluence CVE-2026-90436 response
Check Remote API exposure and update affected systems to 9.2.28 or a current unaffected 10.x release.
For
Confluence Data Center administrators
Sharing
TLP:CLEAR

The condition matters as much as the version. Atlassian lists Confluence Data Center 1.x through 9.x as affected, but says the relevant setting was disabled by default for new installations starting in 3.0. An administrator could later enable it, so verify the running configuration on each instance.

CVE-2026-90436 Exploitation: What Rapid7 Observed

Rapid7 MDR describes exploitation against Confluence Data Center in one customer environment on 13 November. That is a direct observation, not a count of affected organizations. The report supports an urgent response for exposed deployments; each organization still needs its own evidence review.

Rapid7 separately says N-able reported N-central exploitation of a vulnerability that strongly correlates with CVE-2026-90436. That wording does not establish that every N-central exploit chain used this CVE. Keep the two products and their vendor instructions separate when triaging alerts.

Brandefense Blackhole counted three dark-chat posts mentioning CVE-2026-90436 from 19 August through 17 November 2026. The measured unit is posts, not attacks or unique targets.

Confluence evidence as of 17 November 2026
Exploit signals
  • Rapid7 MDRYesExploitation observed in one Confluence customer environment13 Nov 2026
  • Brandefense BlackholeYesThree dark-chat posts mention the CVE; posts are not attacks17 Nov 2026
  • GitHub searchYesOne public repository named for the CVE; code not assessed16 Nov 2026
Verdict Rapid7 observed exploitation; counts are not incidents

Which Confluence Builds Need the Patch?

Atlassian names Confluence Data Center 9.2.28 as a fixed release and says 10.x removed the affected feature. Atlassian Cloud sites are unaffected. The vendor advises updating affected installations to the latest version or a fixed LTS release, then checking the actual running build.

Deployment Condition Action
Data Center 1.x to 9.x Remote API enabled Move to 9.2.28 or a current unaffected release
Data Center 10.x Feature removed Confirm the running version
Atlassian Cloud Unaffected No action for this issue

Atlassian rates the Confluence issue Critical at CVSS 4.0 9.3. NVD lists a secondary CVSS 3.1 score of 9.8 for the underlying Apache Axis CVE. These are different assessments, so do not present the NVD number as Atlassian’s product score.

Do This Now: Patch, Disable, Investigate

Inventory internet-accessible Confluence Data Center instances first, then internal ones. Record the version, owner, Remote API setting, and last verified update. Use Atlassian’s affected-configuration and fixed-version guidance when setting remediation priorities.

Confluence response order
  • Identify installationsRecord build, network exposure, and Remote API state.
  • Patch affected buildsInstall 9.2.28 or a current unaffected release.
  • If patching waitsDisable Remote API in Further Configuration and verify it stays clear.
  • Investigate exposurePreserve logs and examine previously exposed hosts for compromise.
  • Confirm completionCheck the running build and document any remaining exceptions.

If updating must wait, Atlassian advises clearing Remote API (XML-RPC & SOAP) in Further Configuration. The change takes effect without restarting Confluence. Atlassian warns that scripts, automations, and add-ons using that API may stop working, so coordinate the change with their owners.

Apache’s CVE description says Axis can load a class while processing a SOAP fault before service authentication handlers run. With a suitable class present, that behavior may permit remote code execution. The Confluence setting determines whether that library path is exposed in this product.

Atlassian advises security teams to check affected instances for evidence of compromise. Preserve application and host logs before cleanup, and compare suspicious activity with normal maintenance. Follow a patch management process that verifies the installed build after deployment; a queued change alone does not show protection.

Rapid7 recommends emergency remediation for exposed systems. Confirm both the configuration and the build, then document what the available logs can establish about prior exposure. Revisit Atlassian’s advisory if your team uses a supported LTS branch other than 9.2.

Frequently Asked Questions

What should Confluence administrators check first?

Check each Data Center instance’s version, network exposure, and Remote API (XML-RPC & SOAP) setting. Prioritize exposed installations with that setting enabled.

Can disabling Remote API be a temporary mitigation?

Yes. Atlassian says clearing the setting takes effect without a restart, but integrations using the API may stop working. Verify the setting after saving.

What does the N-central report establish?

Rapid7 says N-able reported exploitation of a vulnerability strongly correlated with CVE-2026-90436. This does not prove every N-central chain used the same CVE.

Sources

  1. Rapid7: Detected exploitation of CVE-2026-90436 against Confluence Data Center
  2. Atlassian: CVE-2026-90436 remote code execution in Confluence Data Center
  3. NVD: CVE-2026-90436 record
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →