What is Atlassian CVE-2026-21589?
Atlassian's security advisory, published October 5, 2026, says an unauthenticated attacker can read specific files in the web application root directory of several Data Center products using .. path sequences. The attacker must know the exact file name and path, and directory listing isn't possible, but some configurations hold sensitive files that make the flaw highly severe. Atlassian Cloud is already patched.
Atlassian rates it CVSS 4.0 9.3; NVD shows CVSS 3.1 7.5. CISA added CVE-2026-21589 to its Known Exploited Vulnerabilities catalog on October 15, 2026, with an October 18 due date. Atlassian no longer releases binary patches, so the fix is an upgrade.
Which Atlassian products and versions are affected?
- Data Center versions of Bitbucket, Confluence, Jira Software, Jira Service Management, Bamboo and Crowd, plus Crucible and Fisheye, before the fixed versions.
- Fixed versions include Bitbucket 9.4.26, 10.2.8 and 10.5.1; Confluence 9.2.26 and 10.2.19; Jira Software and Jira Service Management 10.3.26 and 11.3.12; Bamboo 10.2.24 and 12.1.12.
- Not affected: Atlassian Cloud.
How to check if you're affected
- Compare each Data Center product's version with the fixed versions in Atlassian's advisory.
- Search access logs for
..next to/,\or::, including URL-encoded forms. Atlassian suggests URL-decoding each request line up to two times. - Check whether any sensitive files sit in the web application root of your installations.
What to do now
- Upgrade each product to a fixed version or later.
- If you can't upgrade right away, take the instance off the public internet.
- As a stopgap, block URLs containing
..next to/,\or::at a WAF or proxy, or apply the Tomcat or Bitbucket rewrite rules from Atlassian's advisory on every node.
Why the web root is a poor place for secrets
File-read bugs usually can't list directories, so attackers target files they know exist: configuration files, backups and credentials that ship in predictable paths. Keep secrets and backups outside the web root, and read them from a secrets manager or environment instead. That turns many file-read bugs from critical into minor.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify is threat-aware: when an actively exploited vulnerability affects technologies you use, related findings move up your backlog and serious disclosures trigger a threat investigation. Patching self-hosted platforms stays with the team that runs them.
This is a patch for a self-hosted platform, usually owned by an IT or platform team.
Frequently Asked Questions
Which Atlassian products are affected by CVE-2026-21589?
Data Center versions of Bitbucket, Confluence, Jira Software, Jira Service Management, Bamboo and Crowd, plus Crucible and Fisheye, before the fixed versions Atlassian lists. Atlassian Cloud is already patched.
Can I mitigate CVE-2026-21589 without upgrading?
Atlassian suggests taking the instance off the internet, or blocking URLs with .. next to slashes or :: at a WAF or proxy, or applying its Tomcat or Bitbucket rewrite rules. Upgrading is the real fix.
Is CVE-2026-21589 exploited in the wild?
Yes. CISA added CVE-2026-21589 to its Known Exploited Vulnerabilities catalog on October 15, 2026, which means it has evidence of active exploitation. It gave US federal civilian agencies until October 18 to fix it. Treat exposed Atlassian Data Center instances as urgent.
Update Log
- Nov 17, 2026: page published from the primary sources linked above.