Rapid7 says its managed detection team saw the Apache Axis flaw CVE-2026-90436 exploited against Atlassian Confluence Data Center in a customer environment on 13 November 2026.
In an Emergent Threat Response post first published at 18:16 GMT on 16 November and updated on 17 November with an “MDR observed exploitation” section, Rapid7 wrote: “On November 13, 2026, Rapid7 MDR detected exploitation of CVE-2026-90436 against Atlassian Confluence Data Center in a customer environment.” The Apache Software Foundation had disclosed the flaw on 6 November as “a critical unsafe reflection vulnerability (CWE-470) in Axis 1.x that allows for unauthenticated remote code execution.” “CISA has assigned CVE-2026-90436 a CVSS score of 9.8 Critical,” Rapid7 said, citing a CVSS 3.1 vector. Axis 1.x has reached end of life, and “Apache does not plan to publish a fixed Axis 1.x release.”
Atlassian’s security advisory, released at 22:00 PST on 9 November 2026 (06:00 GMT on 10 November) and last modified on 10 November, rates the same issue as critical, with a CVSS 4.0 score of 9.3, “per our internal assessment.” The two figures are not interchangeable: 9.8 is CISA’s CVSS 3.1 score; 9.3 is Atlassian’s CVSS 4.0 score. Atlassian says Confluence Data Center versions 1.x through 9.x are affected only if “Remote API (XML-RPC & SOAP)” is enabled. That setting “was turned off by default for new installations starting in Confluence 3.0” and “was fully removed in Confluence 10.0.” There is “no impact on Atlassian Cloud sites,” and Confluence 10.x and later “are not impacted.” The advisory does not itself report exploitation. “Atlassian cannot confirm if your instances have been affected by this vulnerability,” it says, and tells administrators to have their security teams check affected instances for evidence of compromise.
As of CISA’s Known Exploited Vulnerabilities catalogue version 2026.11.17, dated 17 November 2026, 17:53 GMT, CVE-2026-90436 is not listed.
What Rapid7 says it saw, and the practical fixes
Rapid7’s account is of a single customer environment. It says the operators’ commands “carried sequential task IDs, a structure that suggests the use of AI-assisted automated tooling,” and later describes scripts as “likely AI-generated.” Those are Rapid7’s inferences, not a finding that a named AI product was used. Rapid7 says that just over three minutes after the first observed execution the operators were authenticating to MySQL with Confluence’s own database credentials; that scripts then “hunted for payment card numbers, using Luhn checks”; that “roughly four hours after the first exploit request, the attacker had acquired a service account credential and began querying a production cloud data warehouse”; and that about twelve hours in, an integration service account was used to sign in to Microsoft 365 “using legacy authentication.” Rapid7 recommends remediating exposed systems “on an emergency basis outside of normal patching cycles.”
The practical fixes sit in the Atlassian advisory and are repeated by Rapid7. Affected Data Center customers should upgrade to 9.2.28, the listed fixed version, or to a current 10.x release, in which the Remote API feature has been removed. If a patch has to wait, Atlassian says administrators can turn off “Remote API (XML-RPC & SOAP)” and then check that <base_url>/plugins/servlet/soap-axis1/confluenceservice-v2 returns “HTTP Status 403 – Forbidden.” Turning the setting off, Atlassian warns, “may cause certain functionality, such as scripts, automations and third-party add-ons, to stop working.” Rapid7 also says administrators should investigate systems that had the relevant API enabled for signs of compromise. TSN is not reprinting the indicators of compromise from Rapid7’s post.
The same Axis library sits behind a separate N-able N-central issue that TSN has already covered, including N-able’s instruction to disable the Legacy API and the later 2026.4 HF3 update. That is context only. This post is about Rapid7’s Confluence observation, not a second pass over the N-central case. It sits closer to other recent TSN accounts of exploited remote-access and collaboration software, including Huntress’s finding that a ScreenConnect flaw was used against technicians and TSN’s 8 October cyber-breaches roundup.
A single MDR case is not a KEV listing
Rapid7 is describing one intrusion that its MDR team handled on 13 November, in a customer environment it does not name. That is a serious, specific observation. It is not the same thing as a vendor statement that Confluence instances in general have been breached, and it is not a CISA decision to add the CVE to the Known Exploited Vulnerabilities catalogue. Atlassian’s advisory, last modified three days before Rapid7 first published, still says the company cannot confirm whether instances have been affected. Those three facts can sit together: Rapid7 says it saw exploitation; Atlassian has not independently confirmed it; and as of catalogue 2026.11.17 the flaw is not on the KEV list.
The “AI-assisted” language should be read with the same care. Rapid7 says the structure of the commands “suggests” automated tooling, and that some scripts were “likely AI-generated.” It does not identify a model, a product or a named operator. Treating that wording as proof of an AI-run campaign would go further than the post.
The scores are easier to keep straight than they first look. CISA’s 9.8 is a CVSS 3.1 rating. Atlassian’s 9.3 is a CVSS 4.0 rating of the same vulnerability, offered as the company’s own assessment. Neither figure, on its own, tells an administrator whether a given server is exposed. The configuration test does: the instance is in scope only if Remote API is on, a setting that has been off by default since Confluence 3.0 and is gone in 10.x. The immediate work, for anyone still on an affected 1.x-to-9.x Data Center release, is the one Atlassian and Rapid7 both point to — move to 9.2.28 or 10.x, or disable the Remote API and confirm the 403 — and then look for signs of compromise on anything that had the interface enabled.
Sources
- Rapid7, “Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited,” 16 November 2026, 18:16 GMT, updated 17 November 2026.
- Atlassian, “CVE-2026-90436 – Remote Code Execution in Confluence Data Center,” advisory released 9 November 2026, 22:00 PST, last modified 10 November 2026.
- CISA, Known Exploited Vulnerabilities catalogue, version 2026.11.17, dated 17 November 2026, 17:53 GMT.
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
Huntress Finds ScreenConnect Flaw Exploited Against Technicians is the closest recent TSN account of a vendor-observed exploitation of remote-management software, and is the next read.
- N-able Says Disable N-central Legacy API and Check Servers
- Cyber breaches, 8 October: court files, hijacked domains, a patched-but-probed flaw, church records and a $10m reward
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X




