Skip to content
Reachability Analysis

CVE-2026-21589: Atlassian Data Center products, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

The listed Atlassian products serve web resources through a shared path-handling component. A crafted request can step outside the folder meant to be served and return other files from the web application root, such as configuration files under WEB-INF. Atlassian calls it arbitrary file access (CWE-552); the watchTowr researchers describe it as a pre-authentication arbitrary file read.

The attacker needs no login. They must already know the exact name and path of the target file, and the flaw cannot list directories. How bad it gets depends on what sits in the web root. Atlassian says some configurations hold sensitive files there. watchTowr gave the example of the Crowd client file crowd.properties, which stores the application name and password that Jira, Confluence and others use to talk to Crowd.

Atlassian rates it 9.3 (CVSS 4.0 base score; network, no privileges, high confidentiality impact on the product and high subsequent impact). The flaw reads files only; it does not write or run code by itself.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
a self-managed Data Center, Crucible or Fisheye install runs below its fixed buildRead the version from the product's administration System information page and compare it with the versions table. If you run the software yourself, it is in scope; Atlassian Cloud sites need no action, and Atlassian reported no evidence of exploitation there.
an attacker can reach the web application and no WAF or rewrite rule blocks parent-directory sequencesFrom an untrusted network position, confirm the product's base URL answers through your reverse proxy, load balancer or firewall. Atlassian says instances reachable from the internet, including those with user authentication, should be restricted until you act. Then check your WAF or proxy for the vendor regex (Option 1 in Mitigation). On the host, check conf/server.xml for the RewriteValve line and WEB-INF/rewrite.config for the rule (Confluence, JSM, Jira, Bamboo, Crowd), or the first rule in app/WEB-INF/urlrewrite.xml (Bitbucket).
sensitive files exist under the web application rootList what sits under WEB-INF and the other served folders (for example confluence/WEB-INF, atlassian-jira/WEB-INF, crowd-webapp/WEB-INF, app/WEB-INF) and look for credentials in config files, such as crowd.properties. Without such files the impact is lower, though the flaw is still present.

Affected and fixed versions

Atlassian's advisory table says 'All versions are affected' and tells you to patch to the fixed LTS version or later. If your release line is not listed, move to the nearest fixed line. The 'introduced' versions are from Atlassian's description in NVD. The NVD CPE ranges are narrower for Bitbucket (from 7.17.0) and Jira Service Management (from 4.14.0); older releases of those two are below the fixed builds and fall under the advisory's 'all versions'. Atlassian's security bug fix policy ships fixes as back-ported maintenance releases, not binary patches. Confluence: NVD ranges and Atlassian's fixed list stop at 10.2.19 (the LTS). Atlassian names no separate fix for Confluence 10.3 and later feature releases, states that all versions prior to the listed fixes are affected, and recommends patching to the fixed LTS version or the latest version, so on 10.3 or later move to the latest Confluence release.
ProductAffectedFirst fixed (per supported release line)
Bitbucket Data CenterAll versions before the fix (introduced in 4.6.0). NVD ranges: 7.17.0 up to but excluding 9.4.26; 9.5.0 up to but excluding 10.2.8; 10.3.0 up to but excluding 10.5.19.4.26, 10.2.8, 10.5.1
Confluence Data CenterAll versions before the fix (introduced in 5.10.0). NVD ranges: 5.10.0 up to but excluding 9.2.26; 9.3.0 up to but excluding 10.2.199.2.26, 10.2.19
Jira Service Management Data CenterAll versions before the fix (introduced in 3.1.0). NVD ranges: 4.14.0 up to but excluding 5.12.40; 5.13.0 up to but excluding 10.3.26; 10.4.0 up to but excluding 11.3.125.12.40, 10.3.26, 11.3.12
Jira Software Data CenterAll versions before the fix (introduced in 7.1.0). NVD ranges: 7.1.0 up to but excluding 9.12.40; 9.13.0 up to but excluding 10.3.26; 10.4.0 up to but excluding 11.3.129.12.40, 10.3.26, 11.3.12
Bamboo Data CenterAll versions before the fix (introduced in 7.0.1). NVD ranges: 7.0.1 up to but excluding 10.2.24; 11.0.0 up to but excluding 12.1.1210.2.24, 12.1.12
Crowd Data CenterAll versions before the fix (introduced in 2.11.0). NVD ranges: 2.11.0 up to but excluding 6.3.7; 7.0.0 up to but excluding 7.0.3; 7.1.0 up to but excluding 7.1.7; 7.2.0 up to but excluding 7.2.46.3.7, 7.0.3, 7.1.7, 7.2.4
CrucibleAll versions before the fix4.9.15
FisheyeAll versions before the fix4.9.15

If the fix cannot go in yet

  • Upgrade to a fixed LTS version or later (versions table). Atlassian recommends removing the instance from the internet until it is patched. Cost: downtime for the upgrade, and removing public access stops external users and integrations.
  • Option 1, all products: block any URL that matches this pattern at the WAF or proxy: (?is).*(?:/|\\|::|%(?:25)*(?:2f|5c)|(?::|%(?:25)*3a){2})(?:\.|%(?:25)*2e){2}(?:/|\\|::|%(?:25)*(?:2f|5c)|(?::|%(?:25)*3a){2}|;|%(?:25)*3b|$).* The aim is to block two dots next to a slash, backslash or double colon, including URL-encoded and double-encoded forms. Test that the rule blocks those forms. Cost: any legitimate URL containing such a sequence will be denied.
  • Option 2, Confluence, JSM, Jira, Bamboo and Crowd: back up, then on each node shut it down, add <Valve className="org.apache.catalina.valves.rewrite.RewriteValve" /> inside the application's Context element in conf/server.xml (for Crowd, apache-tomcat/conf/Catalina/localhost/crowd.xml or apache-tomcat/conf/server.xml, whichever holds the Context), then add the vendor's rewrite.config rules to the product's WEB-INF directory (confluence/WEB-INF, atlassian-jira/WEB-INF, bamboo/WEB-INF or atlassian-bamboo/WEB-INF, crowd-webapp/WEB-INF) and restart. Each rule pairs a RewriteCond using the regex above against %{REQUEST_PATH} (and a second against %{REQUEST_URI} as a raw fallback) with RewriteRule (?s)^.*$ /?denied [F,L]. Cost: every node needs a restart, and denied URLs return a forbidden response.
  • Option 3, Bitbucket only: back up, then add a new rule as the first entry in app/WEB-INF/urlrewrite.xml on every node, mirror and mirror farm node, with the regex above in its from element, status 404, and target /mvc/error404, then restart Bitbucket. Cost: a restart on every node; matching requests receive a 404.

What to look for

  • Atlassian cannot confirm whether an instance was affected and tells you to involve your security team to check all affected instances for signs of compromise.
  • Decoded pass: URL-decode each access-log request line, up to two passes, then look for two dots directly next to a slash, backslash or double colon. For example: python3 -c "import sys,urllib.parse as u; [print(u.unquote(u.unquote(l)),end='') for l in sys.stdin]" < access.log | grep -E '(/|\\|::)\.\.(/|\\|::|;|$| )'. A decoded hit looks like GET /<context>/<served-folder>/../WEB-INF/<file> HTTP/1.1 with a 200 status and a response size above zero.
  • Raw pass: search the undecoded lines with the vendor regex, which also matches single and double encoded forms: grep -Pi '(?:/|\\|::|%(?:25)*(?:2f|5c)|(?::|%(?:25)*3a){2})(?:\.|%(?:25)*2e){2}(?:/|\\|::|%(?:25)*(?:2f|5c)|(?::|%(?:25)*3a){2}|;|%(?:25)*3b|$)' access.log.
  • For hits that returned content from WEB-INF, rotate any credentials stored in files under the web root, for example the Crowd application password in crowd.properties.
  • Atlassian and CISA have published no indicator addresses or file hashes.

The earliest dated mark of exploitation is CISA's, on 15 Oct 2026, 10 days after disclosure; exploitation may have begun earlier.

Exploitation reported so far

Neither CISA nor Atlassian gives an exploitation date for Data Center, and KEV lists ransomware use as unknown. For Cloud, Atlassian says its investigation found no evidence of exploitation.

Why static reachability settles it

Whether you are exposed comes down to checkable facts: the product version against the fixed build, whether the web application is reachable, whether a rewrite or WAF rule is in place, and whether sensitive files sit under the web root. Each can be read from the host or the network without running an attack. Because it is known exploited, an affected reachable instance should be patched first and then reviewed for exposed credentials. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-21589: NVD record, read 19 Nov 2026
  2. CVE-2026-21589: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-21589: Atlassian security advisory (vendor advisory, all eight products), read 19 Nov 2026
  4. CVE-2026-21589: watchTowr Labs research, 6 Oct 2026, read 19 Nov 2026
  5. CVE-2026-21589: GitHub advisory database entry GHSA-gr66-x5pq-8g2g, read 19 Nov 2026

Last reviewed 19 Nov 2026.