Atlassian vulnerabilities in 2026: Confluence Data Center and CVE-2026-90436 (not a breach of Atlassian)
Atlassian makes Confluence and Jira, which many companies run on their own servers as Data Center editions. Those servers often hold credentials, runbooks and integration tokens, so a flaw in them reaches well beyond the wiki. This page tracks vulnerabilities in Atlassian's self-managed products that security leaders need to act on.
Short answer
Was Atlassian hacked?
No, CVE-2026-90436 is not a breach of Atlassian: nothing reported shows an intrusion at Atlassian, and Atlassian Cloud is not affected. It is a vulnerability in Apache Axis, a third-party library Confluence Data Center used for its XML-RPC and SOAP Remote API. Atlassian's advisory says Confluence Data Center 1.x to 9.x are affected when "Remote API (XML-RPC & SOAP)" is enabled, rates it critical (CVSS 4.0 9.3, its own assessment) and lists 9.2.28 as the fix; Confluence 10.x removed the feature.
Rapid7 says it detected exploitation against a Confluence Data Center server in a customer environment and responded on 13 November 2026, and CISA added the CVE to its Known Exploited Vulnerabilities catalog on 18 November with a due date of 21 November.
Timeline at a glance
9 Nov 2026Atlassian advisory: Confluence Data Center 1.x to 9.x with the Remote API enabled affected by CVE-2026-90436; fixed in 9.2.28; Cloud and 10.x not affected. (Atlassian)Not a breach
13 Nov 2026Rapid7 MDR responds to exploitation against Confluence Data Center; attacker searched pages for secrets and moved on to cloud accounts. (Rapid7)Reported
17 Nov 2026Java4Shell (CVE-2026-114938, a Java runtime flaw): Calif says it demonstrated pre-login code execution on Jira and Confluence in testing; no Atlassian advisory by 19 Nov. (Calif (via PlayCISO))Reported
18 Nov 2026CISA adds CVE-2026-90436 to the KEV catalog, due 21 November 2026. (CISA)Not a breach
Last updated 19 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.
Atlassian incident timeline, in detail
Confirmed = acknowledged by Atlassian, a regulator filing or a court. Reported = credible reporting Atlassian has not fully confirmed. Unverified claim = an attacker or leak-site claim.
Nov 2026Not a breachProduct vulnerability (third-party library), known exploited
CVE-2026-90436: remote code execution in Confluence Data Center through Apache Axis, known exploited
What happened. Confluence Data Center's XML-RPC and SOAP Remote API used Apache Axis 1.x, which can be made to load and instantiate an attacker-chosen class before authentication. Atlassian says the Remote API has been off by default for new installations since Confluence 3.0 and was removed in 10.0. Workaround: turn off "Remote API (XML-RPC & SOAP)" under General Configuration, Further Configuration (no restart; may break scripts and add-ons).
Impact. Unauthenticated code execution as the Confluence service account. In the intrusion Rapid7 handled, the attacker searched the database, pages and attachments for credentials and keys, attempted AS-REP roasting against a domain controller (Rapid7 says it failed), and within hours used service-account credentials against a cloud data warehouse and Microsoft 365. Atlassian's advisory does not itself say the flaw is exploited.
Severity: Atlassian rates it CVSS 4.0 9.3 (its own assessment); CISA's enrichment of the CVE record gives CVSS 3.1 9.8.
Exploitation: Atlassian's advisory (last modified 10 November) does not mention exploitation; Rapid7 reports it and CISA lists it in KEV.
Java4Shell: Calif's claim of pre-login code execution on Jira and Confluence is a researcher demonstration of a Java runtime flaw, not confirmed by Atlassian as of 19 November 2026.
The pattern across the record
Old integrations keep old code reachable
The Remote API has been off by default for new installs for years. Servers are exposed because someone turned it on for an integration and nobody turned it off.
A wiki is a secrets store
Rapid7's case went from Confluence to a cloud data warehouse and Microsoft 365 in hours, using credentials the server could read.
What it means for Atlassian customers — and what to do
If you run Confluence Data Center, the question is your version and whether the Remote API is on, not whether Atlassian was breached.
1.Patch or turn off the Remote API
Upgrade to 9.2.28 or a current 10.x. Until then, turn off "Remote API (XML-RPC & SOAP)" and confirm Atlassian's check returns HTTP 403.
Any server with the Remote API on after 6 November: look for Java spawning shells, web shells and odd outbound connections, and review sign-ins by accounts whose secrets Confluence holds.
No breach of Atlassian is reported. CVE-2026-90436 is a flaw in the Apache Axis library used by on-premises Confluence Data Center; Atlassian Cloud is not affected.
Which Confluence version fixes CVE-2026-90436?+
Atlassian lists 9.2.28. Confluence 10.x removed the Remote API and is not affected.
Is the Confluence flaw exploited?+
Yes. Rapid7 says it detected exploitation against Confluence Data Center, and CISA added the CVE to KEV on 18 November 2026, due 21 November.
Is Jira affected by CVE-2026-90436?+
Atlassian's advisory covers Confluence Data Center only. It does not list Jira.
More in the Breach Index
Same sourced, verification-tagged timeline, company by company — compare how peers have fared.
Independent analysis for security-leadership education; not affiliated with or endorsed by Atlassian. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.