Skip to main content
All incident reports
Incident report

Atlassian Data Centre flaw exploited within hours of public details

A critical file-access flaw in Atlassian's self-hosted Data Centre products is being exploited soon after technical details became public. Atlassian has released fixes, and researchers warn that stolen configuration files can lead to administrative access in some setups.

· First published

The short version

  • The flaw. CVE-2026-21589 is a critical arbitrary file-access vulnerability, rated 9.3, in multiple self-hosted Atlassian Data Centre products. Atlassian says an unauthenticated attacker can read specific files under the web root only if they know the exact file name and path, and cannot list directories.
  • The exploitation. Previdian's honeypots began recording attempts within two hours of WatchTowr publishing technical details on 6 October. By 7 October Previdian had logged 15 attempts from three IP addresses in Japan and the US; by 8 October it had logged 190 attempts from 32 addresses in 10 countries.
  • The Crowd risk. WatchTowr found that when Jira is integrated with Crowd, an attacker can read a configuration file holding Crowd application credentials in plaintext, then create a user and add it to the Jira administrators group.
  • The response. Atlassian says Cloud products have been patched and has released fixes for the affected self-hosted products. As of 8 October, CISA had not added the flaw to its Known Exploited Vulnerabilities catalogue.

Timeline

DateEvent
5 OctoberAtlassian discloses CVE-2026-21589 and rates it 9.3.
6 OctoberWatchTowr publishes its technical analysis of the flaw.
6 OctoberPrevidian's honeypots begin recording exploitation attempts within two hours of WatchTowr's analysis.
8 OctoberPrevidian reports 190 exploitation attempts from 32 IP addresses in 10 countries.

What happened

Atlassian disclosed CVE-2026-21589 on 5 October and rated it 9.3. The vulnerability affects Bitbucket, Confluence, Jira Software, Jira Service Management, Bamboo, Crowd, Crucible and Fisheye in self-hosted Data Centre deployments. Atlassian says the flaw lets an unauthenticated attacker read specific files under the web application root, but only with prior knowledge of the exact file name and path; it cannot be used to enumerate directories.

WatchTowr published its analysis on 6 October and traced the issue to a library shared by the affected products. Previdian says its honeypots began seeing exploitation attempts hours later. The firm recorded 15 attempts from three IP addresses in Japan and the US by 7 October, and 190 attempts from 32 addresses in 10 countries by 8 October. CISA had not added the flaw to its Known Exploited Vulnerabilities catalogue by 8 October.

The Crowd and Jira path

WatchTowr says the larger risk appears when Jira is integrated with Crowd, Atlassian's identity management product. In that configuration an attacker can read WEB-INF/classes/crowd.properties, which stores Crowd application credentials in plaintext. WatchTowr used those credentials to create a new user and add it to the Jira administrators group.

Fixes and mitigations

Atlassian says Cloud products have been patched. For self-hosted products it has released fixed versions for Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo, Crowd, Crucible and Fisheye. The vendor recommends removing an affected instance from the public internet, applying a Web Application Firewall (WAF) rule, and using rewrite rules for Confluence, Jira Service Management, Jira, Bamboo and Crowd or Bitbucket while patching is completed.

CISA had not added CVE-2026-21589 to its Known Exploited Vulnerabilities catalogue as of 8 October, according to SecurityWeek. Previdian's data shows that exploitation attempts can begin within hours of technical details becoming public.

What is not known yet

  • Who is behind the exploitation attempts and what their objectives are.
  • Whether any organisation has been compromised or had data taken through the flaw.
  • How many internet-facing Atlassian Data Centre instances remain unpatched.
  • Whether any Atlassian Cloud customer data was exposed before the cloud fixes were applied.
  • Whether CISA will add the flaw to its Known Exploited Vulnerabilities catalogue.

What to do

If you run affected Atlassian Data Centre products

  1. Upgrade to a fixed release listed in Atlassian's advisory for each affected product.
  2. If you cannot patch immediately, remove the instance from the public internet.
  3. Apply Atlassian's WAF rule and the rewrite rules for your product as temporary mitigations.
  4. If Jira is integrated with Crowd, treat the integration as high risk and prioritise patching.

For everyone else

  1. Keep an inventory of self-hosted products and versions so you can identify affected systems quickly.
  2. Monitor for exploitation attempts after critical vulnerability details are published.
  3. Treat public exploit details as a trigger to check exposure and patch internet-facing systems first.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.