CVE-2026-21589
Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability
Description
CVE-2026-21589 is a high-severity arbitrary file access vulnerability affecting Atlassian's self-hosted Data Center products — Bitbucket, Confluence, Jira Software, Jira Service Management, Bamboo and Crowd, as well as Crucible and Fisheye. An unauthenticated remote attacker can read specific files inside the web application root directory, provided they already know the exact name and path of the target file; the flaw does not allow directory listing or enumeration. In configurations where sensitive material sits under the application root, this file access vulnerability becomes highly severe, because configuration files, keys and credentials can be retrieved without any login. CISA has added CVE-2026-21589 to the Known Exploited Vulnerabilities catalog, its EPSS score of 12.7% ranks it in the 96th percentile, and its remediation deadline of October 18, 2026 has already passed.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NOpen in CalculatorCWEs
Affected Products
| Vendor | Product | Version |
|---|---|---|
| atlassian | bitbucket data center | >= 7.17.0, < 9.4.26; >= 9.5.0, < 10.2.8; >= 10.3.0, < 10.5.1 |
| atlassian | bitbucket server | >= 4.6.0, <= 8.14.6 |
| atlassian | confluence data center | >= 5.10.0, < 9.2.26; >= 9.3.0, < 10.2.19 |
| atlassian | crowd | >= 2.11.0, < 6.3.7; >= 7.0.0, < 7.0.3; >= 7.1.0, < 7.1.7; >= 7.2.0, < 7.2.4 |
| atlassian | jira data center | >= 7.1.0, < 9.12.40; >= 9.13.0, < 10.3.26; >= 10.4.0, < 11.3.12 |
| atlassian | jira service desk | >= 3.1.0, <= 4.13.27 |
| atlassian | jira service management | >= 4.14.0, < 5.12.40; >= 5.13.0, < 10.3.26; >= 10.4.0, < 11.3.12 |
| atlassian | bamboo | >= 7.0.1, < 10.2.24; >= 11.0.0, < 12.1.12 |
| atlassian | crucible | < 4.9.15 |
| atlassian | fisheye | < 4.9.15 |
References
- https://jira.atlassian.com/browse/BAM-26567(Issue Tracking, Mitigation, Vendor Advisory)
- https://jira.atlassian.com/browse/BSERV-20604(Issue Tracking, Mitigation, Vendor Advisory)
- https://jira.atlassian.com/browse/CONFSERVER-104488(Issue Tracking, Mitigation, Vendor Advisory)
- https://jira.atlassian.com/browse/CRUC-8741(Issue Tracking, Mitigation, Vendor Advisory)
- https://jira.atlassian.com/browse/CWD-6610(Issue Tracking, Mitigation, Vendor Advisory)
- https://jira.atlassian.com/browse/FE-7583(Issue Tracking, Mitigation, Vendor Advisory)
- https://jira.atlassian.com/browse/JRASERVER-79546(Issue Tracking, Mitigation, Vendor Advisory)
- https://jira.atlassian.com/browse/JSDSERVER-16809(Issue Tracking, Mitigation, Vendor Advisory)
- https://github.com/watchtowrlabs/watchTowr-vs-Atlassian-CVE-2026-21589(Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-21589(US Government Resource)
Weakness Type
CWE-552: Files or Directories Accessible to External Parties
This weakness exists when a product makes files reachable by actors who should not have access to them, typically because sensitive material is stored under a web-accessible path without an access control in front of it. In the affected Atlassian products, specific files within the web application root can be fetched by an unauthenticated requester, so whatever an operator has placed or left in that directory is exposed to anyone who knows its name.
Learn more: CWE-552 — Files or Directories Accessible to External Parties
Impact Analysis
CVE-2026-21589 carries a CVSS 3.1 base score of 7.5 (High) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Attack Vector (Network), Privileges Required (None) and User Interaction (None): the request is a plain unauthenticated HTTP fetch against an internet-reachable Atlassian instance, which is how many Data Center deployments are operated for distributed teams. Attack Complexity (Low): no race, no chain and no special setup — the only prerequisite is knowing the file's exact name and path, and attackers work from standard installation layouts and published application file lists rather than guessing. Confidentiality (High), Integrity (None), Availability (None): nothing is modified or destroyed; the entire impact is disclosure. What makes that disclosure serious is what tends to live under an application root in these products — configuration, connection settings, keys and operational artefacts — and that credentials obtained this way feed directly into follow-on authenticated attacks. The EPSS score of 12.7% places CVE-2026-21589 in the 96th percentile, among the most likely vulnerabilities to be exploited, which matches the CISA KEV listing and the fact that the remediation deadline has already passed.
Exploit Maturity
CISA has added CVE-2026-21589 to the Known Exploited Vulnerabilities catalog, confirming exploitation in the wild, with a deadline of October 18, 2026 that has already lapsed; the entry does not flag ransomware usage. Public exploit material is available: the reference set includes the watchTowr Labs repository watchTowr-vs-Atlassian-CVE-2026-21589, so a working detection and exploitation artefact is in the open alongside the vendor's per-product tickets. The EPSS score of 12.7% puts CVE-2026-21589 in the 96th percentile — among the small fraction of vulnerabilities most likely to see exploitation activity — which is consistent with an unauthenticated read on widely deployed, often internet-facing collaboration software. Any Atlassian Data Center, Crucible or Fisheye instance still running an affected version should be considered actively targeted, and operators should assume that files readable through this flaw have already been fetched.
Remediation
- Carry out the action CISA requires, immediately. Apply mitigations in accordance with Atlassian's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of October 18, 2026 has already passed.
- Upgrade every affected product to its fix version. Bitbucket Data Center 9.4.26, 10.2.8 or 10.5.1; Confluence Data Center 9.2.26 or 10.2.19; Crowd Data Center 6.3.7, 7.0.3, 7.1.7 or 7.2.4; Jira Software Data Center 9.12.40, 10.3.26 or 11.3.12; Jira Service Management Data Center 5.12.40, 10.3.26 or 11.3.12; Bamboo Data Center 10.2.24 or 12.1.12; Crucible and Fisheye 4.9.15. The per-product tickets — for example CONFSERVER-104488, JRASERVER-79546 and BSERV-20604 — carry the vendor's mitigation details.
- Take unpatched instances off the public internet. Because no authentication is required, exposure is the precondition: put the application behind a VPN or an authenticating reverse proxy, or block external access at the perimeter until the upgrade is complete.
- Rotate anything that could have been read, and look for retrieval attempts. Treat database credentials, API tokens, SAML and OAuth secrets, license keys and any files kept under the application root as potentially disclosed; rotate them and review web server access logs for unauthenticated requests to unusual file names under the application root.
- Keep sensitive files out of web-accessible directories. As the long-term fix for this weakness class, store configuration and secrets outside the document root, configure the web layer to deny access to file types that should never be served, and audit the application root periodically for backups, exports and leftover artefacts.
Technical Details
The affected Atlassian products serve specific files located inside the web application root directory to requesters that have not authenticated, which is the CWE-552 pattern: the files are in a location the web layer will serve, and no access control stands between the request and the response. Exploitation is therefore a matter of issuing an HTTP request for a known path rather than of defeating a parser or corrupting memory, and the vendor explicitly notes two bounds — the attacker must know the exact file name and path, and the vulnerability provides no directory enumeration or listing capability. Those bounds limit discovery, not impact: the layout of a standard Atlassian installation is public knowledge, so the set of interesting candidate paths is small and well known. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N reflects a remote, trivially repeatable, unauthenticated read with high confidentiality impact and no write or availability consequence, and an unchanged scope because the disclosure stays within the affected application's authority.
Frequently Asked Questions
Is CVE-2026-21589 being actively exploited?
Yes. CISA has added CVE-2026-21589 to the Known Exploited Vulnerabilities catalog, and its remediation deadline of October 18, 2026 has already passed. A public exploitation artefact from watchTowr Labs is available on GitHub, and the EPSS score of 12.7% places the vulnerability in the 96th percentile for exploitation likelihood. Use in ransomware campaigns is not recorded in the KEV entry.
What products are affected by CVE-2026-21589?
CVE-2026-21589 affects Bitbucket Data Center from 4.6.0, Confluence Data Center from 5.10.0, Crowd Data Center from 2.11.0, Jira Software Data Center from 7.1.0, Jira Service Management Data Center from 3.1.0, Bamboo Data Center from 7.0.1, and all versions of Crucible and Fisheye below 4.9.15. Atlassian's older Server editions in those version ranges are affected as well. Atlassian's cloud-hosted offerings are not in the published affected list.
How do I fix CVE-2026-21589?
Upgrade to the fix version for each product: Bitbucket 9.4.26 / 10.2.8 / 10.5.1, Confluence 9.2.26 / 10.2.19, Crowd 6.3.7 / 7.0.3 / 7.1.7 / 7.2.4, Jira Software 9.12.40 / 10.3.26 / 11.3.12, Jira Service Management 5.12.40 / 10.3.26 / 11.3.12, Bamboo 10.2.24 / 12.1.12, and Crucible and Fisheye 4.9.15. Until then, remove public access to the instance, and afterwards rotate credentials and secrets that were stored under the web application root.
How severe is CVE-2026-21589?
CVE-2026-21589 is rated High with a CVSS 3.1 base score of 7.5, driven entirely by confidentiality: an unauthenticated remote attacker can read files, but cannot modify or delete them. Its EPSS score of 12.7% is in the 96th percentile, which is exceptionally high and reflects both the public exploit material and the broad internet exposure of these products. How severe it is for a specific deployment depends on what sits under the web application root — where that includes secrets, the practical impact approaches full compromise.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.