The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-90436: Confluence flaw actively exploited as hackers target servers

By aminah ·17 Nov 2026 ·4 min read
Rows of server racks in a data centre, representing the Confluence Data Center servers targeted through CVE-2026-90436
Hackers are actively exploiting a critical remote code execution flaw in Atlassian Confluence Data Center and N-able N-central, security firm Rapid7 has warned, urging organisations to patch on an emergency basis rather than wait for their normal patching cycle. The flaw, tracked as CVE-2026-90436, is an unsafe reflection vulnerability in Apache Axis 1.x, a Java library used to build web services. It allows an unauthenticated attacker to run code on a vulnerable server without signing in. CISA has assigned it a CVSS score of 9.8, rated critical; Atlassian rates it 9.3 under CVSS version 4.0. The Apache Software Foundation disclosed the flaw on 6 November 2026. It has since emerged that some versions of Atlassian Confluence Data Center and N-able N-central use the affected Axis library and are vulnerable when a specific, non-default configuration is switched on. ## Exploitation confirmed on 13 November Rapid7's managed detection and response team detected exploitation of CVE-2026-90436 against Atlassian Confluence Data Center in a customer environment on 13 November 2026. Separately, on the same day, N-able reported exploitation in the wild against N-central for a vulnerability that strongly correlates to CVE-2026-90436. A proof-of-concept exploit targeting N-central had been published the day before, on 12 November, as part of a series of public zero-day disclosures against N-central. Rapid7 has not described what the attackers did after gaining access to the Confluence system it observed, and has given no victim count beyond the single customer detection. Its published indicators include the IP addresses 192.238.253.176, 5.133.47.243, 163.182.68.109 and 104.13.106.166 for Confluence exploitation. Internet scanning firm Censys reported 1,212,568 internet-facing Confluence web properties in an advisory on 16 November. That figure counts hostname-and-port combinations where Confluence was detected; it does not mean that many installations are vulnerable, because it does not check the software version or whether the setting needed for exploitation is enabled. ## Who is affected and how to fix it Atlassian lists Confluence Data Center versions 1.x through 9.x as affected when the "Remote API (XML-RPC & SOAP)" setting is enabled. The setting has been off by default for new installations since version 3.0. Version 9.2.28 is the fixed release, and affected users should upgrade to it or to a current, unaffected 10.x release. Confluence version 10.x removed the feature, so it is not vulnerable, and Atlassian Cloud is unaffected. If patching must wait, an administrator can disable the setting in General Configuration under Further Configuration, by clearing "Remote API (XML-RPC & SOAP)" and saving. The change takes effect without restarting Confluence, although integrations using the API may stop working. For N-able N-central, administrators should confirm that "Legacy API" is disabled. On 16 November, N-able released N-central 2026.4 HF3, in which the Legacy API feature that exposed the vulnerable Axis attack surface has been disabled. N-central users should upgrade to that release on an emergency basis, outside normal patching cycles. ## No fix for Axis itself Apache Axis 1.x, versions 1.x through 1.4, has reached end of life, and Apache does not plan to publish a fixed Axis 1.x release. Apache recommends moving to another SOAP engine, such as Apache Axis 2, or using an Axis 1.x build with its published patch applied. Organisations using affected products should therefore follow the product vendor's own remediation instructions rather than wait for an Axis update. Rapid7 recommends prioritising internet-accessible instances with the relevant APIs enabled, checking internal deployments as well, and investigating any system that was exposed for evidence of compromise. The presence of the published indicator addresses in logs should prompt investigation, but their absence does not confirm that an environment was unaffected. [Rapid7 reported the exploitation on 16 November 2026](https://www.rapid7.com/blog/post/etr-rapid7-detected-exploitation-of-cve-2026-90436-against-atlassian-confluence-data-center-n-able-n-central-also-exploited/), and [Cyber Security News covered the active exploitation on 17 November](https://cybersecuritynews.com/hackers-exploiting-atlassian-confluence-vulnerability/). ## Frequently asked questions **Is my Confluence server vulnerable?** Only Confluence Data Center versions 1.x to 9.x with the "Remote API (XML-RPC & SOAP)" setting enabled are affected. Confluence Cloud and version 10.x are not vulnerable. **What should administrators do first?** Upgrade Confluence Data Center to version 9.2.28 or a current 10.x release, or disable the Remote API setting immediately if patching must wait. N-central users should upgrade to 2026.4 HF3. **Is there a patch for Apache Axis 1.x?** No. Axis 1.x has reached end of life and Apache will not publish a fixed release, so the fix must come through the affected product vendors.