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.
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.
- 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
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.
- 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.
