US cybersecurity agency CISA lists Atlassian flaw as exploited


A binding US directive requires federal civilian executive-branch agencies to prioritize fixes by risk, while CISA urges other organizations to prioritize listed flaws.
In its 15 October alert, US cybersecurity agency CISA announced that it had added Atlassian vulnerability CVE-2026-21589 to its Known Exploited Vulnerabilities (KEV) Catalog, citing evidence of active exploitation. The designation brings the flaw within an existing risk-based directive for federal civilian agencies; CISA recommends that other organizations also prioritize listed vulnerabilities.
Atlassian disclosed the flaw on 5 October, rating it critical at 9.3 out of 10. It affects eight Data Center products that customers host themselves. The advisory described by The Register on 6 October did not say whether attacks on self-hosted installations had been seen, and Atlassian said it could not confirm whether individual customer installations were affected.
Binding Operational Directive 26-04, titled Prioritizing Security Updates Based on Risk, sets requirements only for Federal Civilian Executive Branch agencies—the civilian executive agencies of the US federal government. CISA says the directive requires rapid remediation of high-risk vulnerabilities while deferring action on lower-risk ones.
The directive specifically prioritizes KEV-listed vulnerabilities on publicly exposed systems when exploitation grants total control of the affected system. That condition matters: catalogue inclusion alone does not establish that every affected Atlassian installation allows a complete takeover. Atlassian describes a file-access flaw whose consequences depend on which sensitive files are accessible.
The directive also sets expectations for when agencies must check whether attackers compromised a system before its patch was applied. CISA's 15 October alert does not specify a remediation deadline for this vulnerability or detail the triggers for those checks.

For organizations outside the directive's federal scope, these are recommendations rather than binding obligations under Directive 26-04. CISA encourages them to manage vulnerabilities according to risk and prioritize remediation of flaws in the KEV Catalog.
In a report dated 7 October, watchTowr separately confirmed active exploitation to The Hacker News. Jake Knott, its head of threat intelligence, said most observed attempts only identified affected products and searched for common configuration files and sensitive information. Such files hold application settings and can contain access credentials. Knott said watchTowr had seen neither further activity after gaining access nor attempts to use credentials obtained through the flaw; those observations did not establish a takeover of customer applications.
The Hacker News reported on 7 October that Previdian had detected 15 exploitation attempts from three distinct IP addresses located in Japan and the US. The attempts targeted its honeypot network—decoy systems used to observe attacks—not confirmed compromises of customer installations. Previdian founder and CEO Ryan Dewhurst said the attempts began within two hours of public exploit details becoming available; the report identified watchTowr's technical publication as that disclosure.
Atlassian says attackers without a login can read specific files in an affected web application's root directory, its top-level folder. They must already know the exact filename and path—the file's location—and cannot use the flaw to list directory contents. Some configurations contain sensitive files that increase the risk, Atlassian warns.
The Hacker News's account of watchTowr's analysis says accessible files could expose credentials, tokens or keys used to authenticate access. In Crowd and Jira configurations with an accessible credentials file, attackers could obtain Crowd credentials and gain administrative access, allowing them to create users, change privileges and make a new user a Jira Administrator. This possible route to application control depends on the files present and accessible; it was not a confirmed outcome of Previdian's 15 detected attempts.
Atlassian listed fixes for all eight products, but The Hacker News reported conflicting version records on 6 October. For Crowd's 7.1 branch, the product ticket's fix-version field said 7.1.7; a table in the same ticket said 7.1.6 and also listed that version as affected. Atlassian's CVE record—the vulnerability entry it filed—listed 7.1.1, released on 27 November 2025, more than 10 months before disclosure. For Bamboo, one CVE field said 10.2.4, while the description and advisory-listed fixes said 10.2.24. These entries should not be treated as interchangeable confirmed fixes.
The CVE record also covers Server, Atlassian's older self-hosted product line, which the advisory does not mention. Atlassian has not said whether Server licenses can run the versions listed as unaffected. Crowd has had no Server release since version 5.2 in September 2023, so none of its listed fixes are Server releases.
| Product | Data Center fixed versions | Server status in the CVE record |
|---|---|---|
| Bitbucket | 9.4.26, 10.2.8, 10.5.1 | Every version affected; no fixed version listed |
| Confluence | 9.2.26, 10.2.19 | Every version affected; no fixed version listed |
| Jira Software | 9.12.40, 10.3.26, 11.3.12 | Versions from 9.12.40 listed as unaffected |
| Jira Service Management | 5.12.40, 10.3.26, 11.3.12 | Versions from 5.12.40 listed as unaffected |
| Bamboo | 10.2.24, 12.1.12 | Every version affected; no fixed version listed |
| Crowd | 6.3.7, 7.0.3, 7.1.7, 7.2.4 | Every version affected; no fixed version listed |
| Crucible | 4.9.15 | Versions from 4.9.15 listed as unaffected |
| Fisheye | 4.9.15 | Versions from 4.9.15 listed as unaffected |
Atlassian's cloud customers do not need to act on this flaw because the company fixed its hosted service, The Register reported on 6 October. The 7 October report also said affected Atlassian Cloud products had been patched.
Atlassian recommends upgrading to a fixed long-term support release—a release maintained for longer—or later. If upgrades must wait, it advises restricting external network access to publicly reachable installations, including those that normally require a login. The company recommends removing installations from the internet where possible until administrators can act, The Register reported on 6 October.
| Products | Temporary protection |
|---|---|
| All eight products | A blocking rule on a web application firewall, which filters web requests, or a reverse proxy, which forwards requests to the application. |
| Confluence, Jira Software, Jira Service Management, Bamboo and Crowd | Also: a Tomcat RewriteValve request-blocking rule in the application's web server. Install it on each server node, shutting down and restarting each one. |
| Bitbucket | Also: a rule in urlrewrite.xml, applied to every node, mirror and mirror farm node, followed by a restart. |
| Crucible and Fisheye | Only the web application firewall or reverse-proxy option is listed. |
The temporary rules block requests whose URL contains two dots (..) immediately beside /, \ or ::, including encoded forms, The Hacker News reports. Atlassian warns that these limited protections do not replace patching.
Atlassian also recommends searching access logs: decode each request line's URL up to twice and look for .. directly beside /, \ or ::, or apply its blocking pattern to raw log lines. That guidance does not distinguish failed attempts from requests that returned files, so a matching request alone does not prove successful file access. It does not explain what further steps customers finding such requests should take after upgrading.
In the 7 October report, Dewhurst forecast that activity would increase quickly as an automated scanning template made mass scanning easier. He urged organizations running affected products to treat patching as an immediate priority.
Following the catalogue addition, federal civilian agencies must apply Directive 26-04's risk-prioritization requirements to affected systems and check for prior compromise when the directive requires it.

NHS England’s review found consent procedures did not follow its digital principles. Its guidance calls for decisions for each patient, rather than blanket use of monitoring technology.
4 min

A fake troubleshooting step activates content already saved on the device. Microsoft advises defenders to watch browser activity and script execution, not just downloads.
3 min

Reports mainly involve Android 10 phones, which meet the published minimum for wired connections. Google has not confirmed a new minimum or cutoff date.
2 min