PoC Exploit Released for Critical Atlassian Flaw That Can Lead to Jira Admin Access

A proof-of-concept exploit chain has been released for CVE-2026-21589, a critical arbitrary file access flaw affecting eight self-hosted Atlassian products.

The research shows that, in deployments integrated with Atlassian Crowd, attackers may be able to steal plaintext application credentials and leverage them to create a Jira administrator account.confluence.

Atlassian disclosed CVE-2026-21589 on October 5, 2026, assigning it a CVSS 4.0 score of 9.3. The issue allows unauthenticated attackers to access specific known files within an affected application’s web application root directory; it does not permit directory listing or arbitrary filesystem access beyond that context.confluence.

Atlassian flaw

The vulnerability affects all versions prior to fixed releases of Bitbucket Data Center, Confluence Data Center, Jira Software Data Center, Jira Service Management Data Center, Bamboo Data Center, Crowd Data Center, Crucible, and Fisheye. Atlassian has issued patches across supported release branches.confluence.atlassian

ProductFixed versions
Bitbucket Data Center9.4.26, 10.2.8, 10.5.1
Confluence Data Center9.2.26, 10.2.19
Jira Software / JSM Data Center9.12.40 or 5.12.40, 10.3.26, 11.3.12
Bamboo Data Center10.2.24, 12.1.12
Crowd Data Center6.3.7, 7.0.3, 7.1.7, 7.2.4
Crucible and Fisheye4.9.15
Impacted Atlassian Product Scope Illustration
Impacted Atlassian Product Scope Illustration (Image Source: watchtowr.com)

According to research published by WatchTowr Labs, the defect was traced to shared Atlassian web-resource code, identifying unsafe handling of a custom :: path encoding scheme.

The vulnerable component converts double colons into forward slashes, creating a path traversal primitive that can bypass checks designed to block conventional ../ traversal sequences.watchtowr

Researchers demonstrated unauthenticated reads of protected files such as WEB-INF/web.xml through resource-download routes in Jira, Confluence, and Bitbucket.

The exact endpoint differs by application, but the underlying flaw resides in shared web-resource functionality, explaining the unusually broad product impact.watchtowr

The vulnerability becomes substantially more dangerous where Jira, Confluence, or another affected platform is integrated with Crowd.

In those configurations, a readable WEB-INF/classes/crowd.properties file may contain the Crowd application name, application password, and service URLs in plaintext, according to the published research.watchtowr

The researchers demonstrated that stolen Crowd application credentials can be used against Crowd’s user-management REST API. An attacker able to reach the Crowd service could enumerate users, create a new account, and add it to the jira-administrators group effectively establishing Jira administrative access.watchtowr

Enterprise Security Expectations vs Reality
Enterprise Security Expectations vs Reality (Image Source: watchtowr.com)

This escalation depends on environmental conditions. Crowd must be integrated with the vulnerable product, the sensitive configuration file must be exposed through the vulnerable application context, and Crowd’s network-access controls must allow the attacker to contact the service.

Strict Crowd IP allowlists can complicate direct exploitation, though they do not eliminate the underlying file-read issue.

WatchTowr has published a Detection Artefact Generator for Jira, Confluence, and Bitbucket. The public tool is intended to identify vulnerable instances rather than serve as a full exploitation framework.github

Organizations should patch affected on-premises and Data Center deployments immediately. If patching cannot occur at once, administrators should remove affected systems from internet exposure or restrict access until updates are applied.securityweek

Security teams should also review whether Crowd is integrated with Jira, Confluence, or Bitbucket; rotate Crowd application passwords; inspect Crowd and Atlassian audit logs for unexpected user creation or group-membership changes; and investigate requests containing anomalous double-colon path sequences.

Atlassian and WatchTowr said there was no evidence of in-the-wild exploitation at the time of reporting, but the released detection material and documented escalation path increase the urgency of remediation.

Trending News

Related Stories