CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-10-06
HIGHCVE-2026-21589exploitedupdatedNATOA1vulnerability

CVE-2026-21589, Atlassian Data Center: unauthenticated arbitrary file access in every version of eight self-managed products, patch or take them off the internet (CVSS 4.0 9.3)

Atlassian's CVE-2026-21589 record, rejected on 16 October, was restored on 19 October; the exploited flaw stands

Defender actions

  • Upgrade every Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo and Crowd Data Center installation to a fixed version of its line (Bitbucket 9.4.26, 10.2.8 or 10.5.1; Confluence 9.2.26 or 10.2.19; Jira Service Management 5.12.40, 10.3.26 or 11.3.12; Jira Software 9.12.40, 10.3.26 or 11.3.12; Bamboo 10.2.24 or 12.1.12; Crowd 6.3.7, 7.0.3, 7.1.7 or 7.2.4) and Crucible and Fisheye to 4.9.15, internet-reachable instances first; until each is upgraded, take it off the internet or put Atlassian's web application firewall or Tomcat rewrite rule in front of it.
  • On every Jira instance that was internet-reachable and unpatched and is integrated with Crowd, treat the Crowd application password in its WEB-INF/classes/crowd.properties as readable: rotate it after the upgrade and review Crowd for user accounts created or group memberships changed since the exposure began; on every affected instance search the web server and proxy logs back to 2026-10-05, the day the advisory published (honeypots recorded the first attempts on 2026-10-06), for '..' next to '/', '\\' or '::'.
  • Confirm that every vulnerability scanner, SIEM enrichment rule and ticket keyed on CVE-2026-21589 reports each affected Atlassian instance as open again; where a feed dropped the ID while the record was rejected between 2026-10-16 and 2026-10-19, re-run it so no exploited instance stays reported as closed.

Analysis

Atlassian's advisory of 2026-10-05 says every version of Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo and Crowd Data Center, and of Crucible and Fisheye, is affected by CVE-2026-21589, an arbitrary file access flaw that lets an unauthenticated attacker access specific files within the web application root directory (Atlassian, 2026-10-05). The attacker needs the target file's exact name and path and cannot enumerate or list directory contents, and Atlassian adds that in some configurations sensitive files are present that increase the risk (Atlassian, 2026-10-05). Atlassian's public ticket for Confluence Data Center labels the weakness "Path Traversal (Arbitrary Read/Write)" (Atlassian, 2026-10-02), while the advisory's CVSS 4.0 vector (9.3, Critical: network, low complexity, no privileges, no user interaction) rates the confidentiality impact high and the integrity and availability impact none on the vulnerable system, with high confidentiality, integrity and availability impact on subsequent systems (Atlassian, 2026-10-05). Atlassian Cloud is already patched (Atlassian, 2026-10-05), and exploitation attempts have been recorded on honeypot sensors since 2026-10-06 (Previdian, 2026-10-16); CISA added the flaw to its Known Exploited Vulnerabilities catalog on 2026-10-15 "based on evidence of active exploitation" (CISA, 2026-10-15). The Register reports that Atlassian emailed customers on Monday pointing to the advisory (The Register, 2026-10-06). The CVE record for this ID was marked rejected on 2026-10-16 (ENISA EUVD, 2026-10-16), while Atlassian's advisory still uses the ID and lists the same fixed versions (Atlassian, 2026-10-05).

The 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; and Crucible and Fisheye 4.9.15 (Atlassian, 2026-10-05). Atlassian's Confluence ticket adds that versions past end of life may also be affected (Atlassian, 2026-10-02), and its Crowd ticket lists the same fixed Crowd builds (Atlassian, 2026-10-02). Until a patch is applied, Atlassian says to remove the instance from the internet where possible, including instances that require user authentication, or to block at a web application firewall or proxy any URL that carries '..' directly next to a slash, backslash or '::' in plain or percent-encoded form; it also gives a Tomcat RewriteValve rule for Confluence, Jira Service Management, Jira Software, Bamboo and Crowd and a urlrewrite.xml rule for Bitbucket (Atlassian, 2026-10-05).

Cited evidence

This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files within the web application root directory in affected versions.

Exploitation requires prior knowledge of the target file's exact name and path; this vulnerability does not allow attackers to enumerate or list directory contents.

Affected Atlassian Cloud products have been patched, and our investigation has not found evidence of exploitation.

Remove your instance from the internet until you can patch or apply mitigations, if possible.

Atlassian 2026-10-05

While we are not able to traverse outside of the Tomcat context, we discovered it is possible to read any file within the application server itself.

The password for the application, in plaintext.

watchTowr Labs 2026-10-06

Within two hours of watchTowr publishing its technical research and public PoC for CVE-2026-21589, Previdian's honeypot network began observing exploitation attempts targeting the vulnerability

BleepingComputer 2026-10-07

Starting yesterday, we saw some exploit attempts hitting our honeypot, using the exploit URLs mentioned in the Watchtowr blog.

SANS Internet Storm Center 2026-10-07

Open source reporting indicates that CVE-2026-21589 is being exploited in the wild.

Canadian Centre for Cyber Security

based on evidence of active exploitation

CISA 2026-10-15

This CVE's publication may have been a false positive or a mistake. As a result, we have rejected this record.

This Arbitrary File Access vulnerability allows an unauthenticated attacker to access specific files within the web application root directory in affected versions.

ENISA EUVD 2026-10-16

Updates5

Update

watchTowr Labs published the root cause on 2026-10-06 after comparing a vulnerable and a fixed build of the web-resource library that Jira, Confluence and Bitbucket share: its router converts a double colon in a request path into a slash before it resolves a plugin resource, so a traversal written with double colons leaves the resource directory through a deprecated relative-path resolver that is still reachable (watchTowr Labs, 2026-10-06). watchTowr says it cannot leave the Tomcat context but can read any file within the application server, and it shows working requests against Jira, Confluence and Bitbucket, with Bitbucket blocking one configuration file but not another under WEB-INF (watchTowr Labs, 2026-10-06).

The impact it demonstrates depends on the configuration: where Jira is integrated with Crowd, the crowd.properties file under WEB-INF stores the application name and its password in plaintext, and with those watchTowr reached Crowd's REST interface in its lab, created a user and added it to the Jira administrators group; it adds that a Crowd IP allow-list would make this harder (watchTowr Labs, 2026-10-06). watchTowr also published a Detection Artifact Generator on GitHub that sends the traversal to Jira, Confluence and Bitbucket hosts to test whether they are vulnerable (watchTowr Labs on GitHub, 2026-10-06). Neither watchTowr's post nor Atlassian's advisory of 2026-10-05 reports exploitation in the wild. Atlassian's Crowd ticket lists the same fixed builds as the advisory, 7.1.7 for the 7.1 line (Atlassian, 2026-10-02).

Update

Exploitation attempts began on 2026-10-06, the day watchTowr published. Previdian, which runs a honeypot network, told BleepingComputer that its sensors began recording attempts within two hours of that publication, and that a Nuclei template has since been released that makes scanning for vulnerable systems easier; it expects exploitation to rise significantly over the coming days and weeks (BleepingComputer, 2026-10-07). As recorded on 2026-10-08, Previdian's telemetry page showed at least 129 attempts from at least 22 source addresses in eight countries across three sensors, from 2026-10-06 to 2026-10-08, and listed the flaw as not in CISA's KEV catalog (Previdian, 2026-10-08). Its timeline still lists the first sensor observation at 21:55 UTC on 2026-10-06, about five hours after watchTowr's post of 17:01 UTC, which is later than the two-hours figure (Previdian, 2026-10-16; watchTowr Labs, 2026-10-06). The SANS Internet Storm Center says its own honeypots began receiving attempts on 2026-10-06 with the URLs from watchTowr's write-up against Jira, Confluence and Bitbucket resource paths, that every source address belongs to one cloud hosting provider, and that it believes a single actor is behind them (SANS ISC, 2026-10-07).

Neither honeypot operator reports a successful compromise. The Canadian Cyber Centre updated its bulletin on 2026-10-07 to say that open-source reporting indicates the flaw is being exploited in the wild (Canadian Cyber Centre, 2026-10-07), while NCSC Switzerland's advisory, edited on 2026-10-07 to add the public proof of concept, then listed the status as proof of concept available without reporting exploitation (NCSC Switzerland, 2026-10-07).

Update

CISA added CVE-2026-21589 to its Known Exploited Vulnerabilities catalog on 2026-10-15, "based on evidence of active exploitation" (CISA, 2026-10-15). The alert does not say what the evidence is, who is exploiting the flaw or whether any attempt succeeded, so neither CISA nor the honeypot operators report a compromise. Previdian's page, updated 2026-10-16, now counts 607 attempts from 65 unique addresses in 20 countries across five sensors between 2026-10-06 and 2026-10-15, and lists the flaw as in the CISA catalog (Previdian, 2026-10-16). NCSC Switzerland edited its advisory on 2026-10-12 to list the status as proof of concept available and actively exploited, citing the attempts Previdian recorded on its honeypot sensors (NCSC Switzerland, 2026-10-12).

Update

ENISA's EUVD record EUVD-2026-92807 for CVE-2026-21589, which names Atlassian as the assigner, was updated at 20:39 UTC on 2026-10-16 and now describes the record only as "This CVE's publication may have been a false positive or a mistake. As a result, we have rejected this record." (ENISA EUVD, 2026-10-16). The same record still lists exploitation since 2026-10-15 (ENISA EUVD, 2026-10-16).

The flaw itself is unchanged: Atlassian's advisory, as read on 2026-10-17, still uses the ID, lists the same fixed versions and carries no note of the rejection (Atlassian, 2026-10-05). No source read says why the record was rejected or whether a replacement ID will follow. The consequence is for tooling: a scanner plugin, SIEM enrichment rule or ticket keyed on the ID, or on a feed that drops rejected IDs, can stop reporting a flaw that is exploited, so track it by Atlassian's advisory and the fixed versions above until a replacement ID appears.

Improvement

ENISA's EUVD record EUVD-2026-92807 for CVE-2026-21589, which named Atlassian as the assigner and carried the rejection sentence from 2026-10-16, was updated at 18:26 UTC on 2026-10-19 and again carries the full vulnerability description and the fixed versions instead of the rejection text; it still lists exploitation since 2026-10-15 (ENISA EUVD, 2026-10-19). Atlassian's advisory, read on 2026-10-20, is unchanged: it uses the same ID, lists the same fixed versions and carries no note on the record's status (Atlassian, 2026-10-05). No source read says why the record was rejected or why it was restored, and no replacement ID exists. The consequence is for tooling: a scanner plugin, SIEM enrichment rule or ticket keyed on the ID, or on a feed that excludes rejected IDs, may have dropped this exploited flaw between 2026-10-16 and 2026-10-19, so re-run them to be sure no affected Data Center instance stays reported as closed.

Sources14

Revision history

  1. Published 2026-10-06T0405Z-intel
  2. Update 2026-10-07T0404Z-intel

    watchTowr Labs published the root cause (a path-separator substitution in the web-resource library shared by Jira, Confluence and Bitbucket), the request shape and a runnable checker on 2026-10-06, and shows that where Jira is integrated with Crowd the file read exposes a plaintext Crowd application password that gives administrator access to Crowd for that application. The flaw moves from a patch-now issue with unpublished mechanics to one with public mechanics and a Crowd credential to rotate; no exploitation is reported. Atlassian's Crowd ticket lists the same fixed builds as the advisory.

    Changed: headline summary tags techniques cves sources evidence verification sourcing_note classification actions body

  3. Update 2026-10-08T0404Z-intel

    Exploitation attempts began on 2026-10-06, the day watchTowr published its write-up and proof of concept: Previdian's sensors have recorded at least 129 attempts from at least 22 addresses in eight countries, SANS ISC recorded similar attempts against Jira, Confluence and Bitbucket on its own honeypots, all from one cloud provider, and a Nuclei template exists; the Canadian Cyber Centre's bulletin now cites open-source reporting of in-the-wild exploitation. The status moves from patch-available to exploited, with no compromise reported and the flaw not listed in CISA's KEV catalog on Previdian's page.

    Changed: headline summary tags techniques cves sources evidence sourcing_note actions body

  4. Update 2026-10-16T0256Z-intel

    CISA added CVE-2026-21589 to its Known Exploited Vulnerabilities catalog on 2026-10-15 on evidence of active exploitation, which moves the flaw from honeypot-observed attempts to government-confirmed exploitation; CISA names neither the evidence, the actor nor any victim, and neither CISA nor the honeypot operators report a compromise; Previdian's honeypot count has grown to 607 attempts from 65 addresses in 20 countries, and NCSC Switzerland has listed the flaw as actively exploited since 2026-10-12.

    Changed: headline summary tags cves sources evidence sourcing_note body

  5. Update 2026-10-17T0256Z-intel

    Atlassian, the assigner, rejected the CVE record for CVE-2026-21589 on 2026-10-16, giving only the generic reason that its publication may have been a false positive or a mistake; ENISA's EUVD record mirrors it and still lists exploitation since 2026-10-15. Atlassian's advisory still uses the ID with the same fixed versions, and no source says why the record was rejected or whether a replacement ID will follow, so tooling keyed on the ID can lose track of an exploited flaw.

    Changed: headline summary sources evidence sourcing_note actions body

  6. Improvement 2026-10-20T0256Z-intel

    ENISA's EUVD record for CVE-2026-21589, which carried the rejection sentence from 2026-10-16, was updated on 2026-10-19 and again carries the full vulnerability description and the fixed versions; exploitation since 2026-10-15 is still listed and Atlassian's advisory is unchanged. Tooling keyed on the ID may have dropped the flaw while the record was rejected and should be re-run.

    Changed: headline summary sources evidence sourcing_note actions body

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.