• Sources: primary, research, discussion
  • Summary: The GitHub advisory record GHSA-gr66-x5pq-8g2g carries the Atlassian advisory text for CVE-2026-21589, rated CVSS v4 9.3 critical under CWE-552, with the base metrics CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N, so attack complexity is low, there are no attack requirements, and no privileges or user interaction are needed. NVD published it on 2026-10-05. The record names eight products: Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo and Crowd in their Data Center editions, plus Crucible and Fisheye, which it does not label Data Center. All versions are affected, back to releases as old as Bitbucket 4.6.0 and Confluence 5.10.0. The fix list reads Bitbucket 9.4.26, 10.2.8 and 10.5.1, Confluence 9.2.26 and 10.2.19, Crowd 6.3.7, 7.0.3, 7.1.1 and 7.2.4, Jira Software 9.12.40, 10.3.26 and 11.3.12, Jira Service Management 5.12.40, 10.3.26 and 11.3.12, Bamboo 10.2.24 and 12.1.12, and Crucible and Fisheye 4.9.15. Atlassian states that exploitation requires prior knowledge of the exact file path and that directory listing is not possible, and watchTowr published a chain that reads one documented path, WEB-INF/classes/crowd.properties, which stores the Crowd application password in plaintext, then uses it to add an attacker-created user to jira-administrators. The vendor advisory page itself was not read on this run, and the two sources disagree on the Crowd fix, with watchTowr listing 7.1.7 against the 7.1.1 in the fix list above.
  • Why it matters: A path-knowledge precondition stops being a mitigation the moment one sufficient path is published, so on an unpatched install the working assumption is that the Crowd credential is already readable rather than merely reachable.
  • Follow-up: The fixed version for Crowd confirmed from the vendor advisory page, and any report of exploitation in the wild.