Critical file access flaw hits Atlassian Jira, Confluence, Bitbucket and other self-hosted products
On 5 October 2026 Atlassian fixed CVE-2026-21589, a flaw that lets an unauthenticated attacker read specific files on several of its self-hosted products. Organisations running Bitbucket, Confluence, Jira, Jira Service Management, Bamboo or Crowd Data Center, as well as Crucible and Fisheye, are affected.
What to do now
- Product
- Atlassian Bitbucket, Confluence, Jira, Jira Service Management, Bamboo, Crowd (Data Center), Crucible, Fisheye
- Affected versions
- All versions earlier than the fixed releases of Bitbucket, Confluence, Jira, JSM, Bamboo, Crowd (Data Center), Crucible and Fisheye
- Fixed in
- Confluence 9.2.26/10.2.19; Jira 9.12.40/10.3.26/11.3.12; Bitbucket 9.4.26/10.2.8/10.5.1; others: see article
- CVE
- CVE-2026-21589
Atlassian released a security advisory on 5 October 2026 for a critical vulnerability tracked as CVE-2026-21589, which CERT-EU has since covered in its advisory 2026-015. The products concerned are Bitbucket Data Center, Confluence Data Center, Jira Software Data Center, Jira Service Management Data Center, Bamboo Data Center, Crowd Data Center, Crucible and Fisheye.
The bug allows arbitrary file access: an attacker with no account can retrieve files stored under the web application's root directory. The attacker must already know the exact name and path of the target file, since the flaw does not allow directory listing. Atlassian warns that some configurations hold sensitive files, which raises the stakes. According to the vendor, Atlassian Cloud has already been patched and its investigation found no evidence of exploitation.
Every version older than the fixed releases is vulnerable. Fixed versions are: Bitbucket Data Center 9.4.26, 10.2.8 and 10.5.1; Confluence Data Center 9.2.26 and 10.2.19; Jira Service Management Data Center 5.12.40, 10.3.26 and 11.3.12; Jira Software Data Center 9.12.40, 10.3.26 and 11.3.12; Bamboo Data Center 10.2.24 and 12.1.12; Crowd Data Center 6.3.7, 7.0.3, 7.1.7 and 7.2.4; Crucible and Fisheye 4.9.15. Atlassian advises moving to the fixed LTS release or later.
Where patching cannot happen right away, the vendor says to take the instance off the internet, even if it requires login. Otherwise there are three workarounds: a WAF or proxy rule blocking '..' next to '/', '' or '::', including URL-encoded forms; enabling Tomcat's RewriteValve with a rewrite.config file for Confluence, Jira, Jira Service Management, Bamboo and Crowd; or a blocking rule in urlrewrite.xml for Bitbucket on every node and mirror. Take a backup before using either of the last two, and use the exact configuration given in Atlassian's advisory.
CERT-EU also asks administrators to review access logs, either by URL-decoding each request and looking for those traversal sequences or by running Atlassian's regular expression over the raw lines. If compromise is suspected, investigate the instances, rotate any credentials or secrets that may have been exposed, and contact the relevant cybersecurity authority.
What to do now
- Upgrade internet-facing instances first to the fixed release for each product (for example Confluence 9.2.26 or 10.2.19, Jira 9.12.40, 10.3.26 or 11.3.12).
- If you cannot patch immediately, remove the instance from the internet or apply one of the workarounds in Atlassian's advisory after taking a backup.
- Search access logs for requests containing '..' next to '/', '\' or '::', in plain or URL-encoded form.
- If you find suspicious entries, rotate credentials and secrets stored on the server and report the incident to your cybersecurity authority.