Actively exploited: CVE-2026-90436 (CVSS 9.8), an unauthenticated RCE in end-of-life Apache Axis 1.x, is being used against Atlassian Confluence Data Center and N-able N-central. Rapid7 MDR saw it against Confluence in a customer environment on November 13, 2026.
- The flaw is unsafe reflection (CWE-470) in Axis 1.x, a SOAP implementation for Java web services, disclosed by the Apache Software Foundation on November 6. Axis 1.x through 1.4 is EOL and Apache does not plan a fixed 1.x release. It recommends moving to another SOAP engine such as Axis 2, or using an Axis 1.x build with the published patch. Downstream products that bundle the library inherit the bug.
- Confluence Data Center: Atlassian lists 1.x through 9.x as affected only when "Remote API (XML-RPC & SOAP)" is enabled, which has been off by default for new installs since 3.0. 9.2.28 is the fixed release. 10.x removed the feature and Atlassian Cloud is unaffected. If you cannot patch yet, an admin can clear the setting under General Configuration > Further Configuration with no restart, but API integrations may break.
- N-able N-central: N-able reported in-the-wild exploitation on November 13 of a vulnerability that strongly correlates to CVE-2026-90436. A public PoC targeting N-central appeared on November 12 as part of a series of zero-day disclosures against the product. The exposure is the Legacy API, off by default, and admins should confirm it is disabled even on 2026.4 HF2. HF3 removes Legacy API access permanently. Hosted upgrades are done, on-prem GA is being finalized, and N-able temporarily disabled the Intune integration. Both hosting models still need to follow the Agent and Probe upgrade guidance.
- Timeline matters for scoping: disclosure November 6, PoC November 12, exploitation observed November 13. Any exposed instance with the relevant API enabled during that window is a candidate for compromise, and internal deployments count too.
- IOCs from the report. Confluence exploitation: 192.238.253[.]176, 5.133.47[.]243, 163.182.68[.]109, 104.13.106[.]166. N-able's November 13 incident update lists these for N-central customers who had not disabled Legacy API: 157.20.241[.]16, 139.99.69[.]109, 79.76.51[.]56. The vendor's update also lists associated URLs for compromise assessment.
Takeaway: patching or disabling the API closes the door but does not tell you whether someone already walked through. Check whether Remote API (XML-RPC & SOAP) on Confluence or Legacy API on N-central was enabled on each instance, then search your logs back to at least November 6 for the IPs above. A hit means start an investigation. A miss proves nothing, since Rapid7 notes that absence of these addresses does not confirm a clean environment. Preserve logs and host evidence before you change settings or upgrade. Since this is RCE, review the application hosts themselves for unexpected child processes, new files, and new accounts. N-central deserves extra attention because it manages downstream endpoints. The report has the Confluence IPs, and N-able's incident update has the N-central IOCs and URLs. Rapid7 recommends emergency remediation outside normal patch cycles.