Skip to content

Vulnerabilities & Patches

Rapid7 reports active exploitation of CVE-2026-90436 in Confluence and N-central

Rapid7 says its MDR detected the flaw against Confluence Data Center on November 13, 2026, with N-able reporting N-central exploitation the same day.

https://breach-signal.com/vulnerabilities/cve-2026-90436-confluence-n-central-exploitation/

Share

Key facts

  • Rapid7 MDR detected active exploitation of CVE-2026-90436 against Atlassian Confluence Data Center.
  • On November 13, 2026, N-able reported wild exploitation against N-central tied to a vulnerability strongly correlating to CVE-2026-90436.
  • Both Atlassian Confluence Data Center and N-able N-central are seeing active in-the-wild exploitation of CVE-2026-90436.
  • Rapid7 says exposed systems should be remediated on an emergency basis outside normal patching cycles.

Rapid7 reports active exploitation of CVE-2026-90436, a critical unauthenticated remote code execution flaw in Apache Axis 1.x, against Atlassian Confluence Data Center and N-able N-central, with Rapid7 MDR detecting it in a customer environment on November 13, 2026.

A proof-of-concept exploit leveraging CVE-2026-90436 against N-central was published on November 12, 2026, during public zero-day disclosures against N-central, and the public PoC publication preceded the observed exploitation by one day. Both Atlassian Confluence Data Center and N-able N-central are seeing active in-the-wild exploitation of CVE-2026-90436. N-able reported wild exploitation against N-central on November 13, 2026, tied to a vulnerability strongly correlating to CVE-2026-90436.

The Apache Software Foundation disclosed CVE-2026-90436 on November 6, 2026, as a critical unsafe reflection vulnerability in Axis 1.x allowing unauthenticated remote code execution, and CISA assigns it a CVSS score of 9.8 Critical. Apache Axis is a SOAP implementation used to create Java Web services. CVE-2026-90436 exposes versions of Atlassian Confluence Data Center and N-able N-central that use the affected Axis library.

Axis 1.x through 1.4 are affected and have reached end of life, so Apache does not plan a fixed release for Axis 1.x through 1.4. Apache recommends moving to another SOAP engine such as Apache Axis 2 or using a patched Axis 1.x build.

Atlassian lists Confluence Data Center versions 1.x through 9.x as affected when Remote API (XML-RPC & SOAP) is enabled, and version 9.2.28 is the fixed release. Confluence Data Center 10.x and later removed the feature and are not vulnerable; Atlassian Cloud is also unaffected; new installations have had Remote API off by default since version 3.0.

Attackers can exploit CVE-2026-90436 against Confluence Data Center or N-central only when a non-default configuration exists in the target product. Defenders should verify whether the relevant APIs are enabled on internet-accessible instances and check internal deployments as well while looking for evidence of compromise. Users affected by the issue should upgrade to a current unaffected 10.x release or version 9.2.28.

If patching must wait, an administrator can open General Configuration and Further Configuration, edit settings, and clear Remote API (XML-RPC & SOAP). The change takes effect without restarting Confluence, but API integrations may stop working after it.

A medieval stone castle stands behind a wooden palisade wall on a sandy shore, surrounded by lush green trees.
A historic stone castle fortified by a wooden palisade represents the concept of building strong defensive barriers when immediate patching is not yet possible. Photo by JOHN K THORNE on Flickr

N-able on-premises administrators should confirm Legacy API is disabled even on version 2026.4 HF2, and the feature is off by default according to N-able’s instructions. N-able says version 2026.4 HF3 will permanently remove Legacy API access, and on-premises administrators should confirm availability and follow release instructions when the HF3 update becomes available.

Hosted environments received temporary protections under N-able’s November 13 guidance, and N-able’s November 16 rollout notice states hosted upgrades are complete and N-able is finalizing on-premises general availability. Customers in both N-able hosting models must follow the vendor’s Agent and Probe upgrade guidance, and N-able temporarily disabled the Intune integration as a precaution.

Observed exploitation against Confluence Data Center is linked to IP addresses 192.238.253[.]176, 5.133.47[.]243, 163.182.68[.]109, and 104.13.106[.]166. N-able’s November 13 incident update flags 157.20.241[.]16, 139.99.69[.]109, and 79.76.51[.]56 for N-central customers that did not disable Legacy API, and associated URLs listed in the update can be used for compromise assessment. Investigate when these IOCs appear in logs, although their absence does not confirm an environment was unaffected.

Rapid7 says exposed systems should be remediated on an emergency basis outside normal patching cycles, prioritize internet-accessible instances that have the relevant APIs enabled and check internal deployments as well while looking for evidence of compromise. Rapid7 initially published this report on November 16, 2026.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *