A critical vulnerability has been discovered in the Data Center versions of Jira, Confluence, and six other Atlassian products, installed on customer data centers. This weakness allows an unauthorized user to read files and potentially gain access to Jira’s administrative interface. Exploit attempts have already been observed, prompting teams to remediate the issue and refresh any secrets that could have been exposed.
Atlassian’s tools are central to IT teams, managing everything from code in Bitbucket to tickets in Jira and documentation in Confluence. A vulnerability in these tools threatens the entire development and support pipeline, with Data Center versions requiring companies to address these issues independently. On October 5th, Atlassian issued a security advisory regarding vulnerability CVE-2026-21589, rating it as critical with a CVSS score of 9.3.
Data Center versions are entering their final years as Atlassian has announced it will sunset this offering by March 28, 2029, pushing clients towards its cloud solutions. Many organizations have opted to retain these on-premises solutions to maintain control over their data and infrastructure. They had previously faced a similar severity alert in June 2022, when a vulnerability in Confluence was exploited shortly after discovery.
Unauthenticated File Reading Across Eight Products
The vulnerability permits an unauthenticated attacker to access specific files located in the web application’s root directory. However, to exploit this, the attacker needs to know the exact file names and paths, as the flaw does not allow directory listing. Atlassian notes that certain configurations may contain sensitive files that increase the severity risk, and that the 9.3 score reflects its assessment which should be evaluated against each client’s environment.
All Data Center versions of Bitbucket, Confluence, Jira Software, Jira Service Management, Bamboo, and Crowd are affected, as well as Crucible and Fisheye, up to patched versions. Atlassian has released patches for each supported branch, including Jira Software versions 9.12.40, 10.3.26, and 11.3.12, as well as Confluence versions 9.2.26 and 10.2.19, with Crucible and Fisheye version 4.9.15 also patched. The cloud products have been secured by the vendor, which reported no evidence of exploitation.
From Crowd Configuration Files to Jira Administration
The vulnerability’s gravity stems from the chaining exploit detailed by researchers from watchTowr Labs on October 6. In a deployment where Crowd manages Jira accounts, the researchers accessed the crowd.properties file, which contains application credentials. With these credentials and network access to Crowd, they were able to create a new user and add that user to Jira’s administrator group. However, a properly configured allowed address list for Crowd could block this pathway.
This disclosure has prompted exploit attempts, with CrowdSec, a French threat detection vendor, reporting 89 distinct IP addresses sending requests corresponding to the vulnerability since October 7, according to its weekly report on October 12. Atlassian cannot confirm whether client instances were affected and recommends that each client review their own access logs.
Emergency Patch and Secret Renewal
The immediate priority is to apply the patch outside of normal update cycles. Companies unable to implement the fix immediately should, according to Atlassian, remove the instance from the internet, even if it is protected by user authentication. As an alternative, the vendor suggests deploying a web application firewall rule or address rewrite to block malicious requests. Security firm Rapid7 reminds that these workarounds reduce risk but do not replace the need for a patch.
The patch does not mitigate any access issues that may have occurred prior to its application. Atlassian advises searching logs for specific sequences “..” adjacent to a slash as a signal of an attempt to traverse the directory structure. Rapid7 suggests that if access to configuration files is detected, it is crucial to renew credentials and other exposed secrets after isolating the relevant systems, starting with Crowd.
Atlassian Data Center: Control Comes with Responsibility
For CIOs who have retained Atlassian, this vulnerability serves as a reminder of the price of such a choice. Maintaining control over data and infrastructure comes with the responsibility to act swiftly, unlike cloud clients who face no immediate actions. This episode will influence the decision-making process that must occur ahead of the Data Center’s termination in 2029, without altering the reasons for keeping on-premises solutions, which are more about sovereignty and data control than simply the security of a patch.
Beyond the immediate choice, the response needs to extend beyond just Atlassian servers. The application identifiers within Crowd connect to the directory that governs Jira, and refreshing these credentials should be handled as a privileged account renewal. Teams still exposing Jira, Confluence, or Bitbucket to the internet should prioritize restricting access even after applying the patch, as these tools host the company’s code, tickets, and documentation.



