Atlassian Flaw CVE-2026-21589 Lets Attackers Read Files Without Logging In, Across Jira, Confluence and Bitbucket
Atlassian has published an out-of-band critical advisory for CVE-2026-21589, a vulnerability affecting numerous on-premises Atlassian products. Atlassian describes it as "Arbitrary File Access", but researchers at watchTowr Labs say this means arbitrary file read. The severity score shows that an attacker needs no authentication and no special conditions.
The scale is the concern. The flaw affects all previous versions of the listed products, and watchTowr notes that a quick internet search finds just under 700,000 Confluence instances alone. Their estimate is that the total exposure across products is in the six to seven-figure range.
Because so many products are affected, the researchers reasoned that they must share a common component. After comparing vulnerable and patched copies of Bitbucket, Confluence and Jira, one library stood out: atlassian-plugins-webresource. Atlassian's suggested WAF rules also offered a clue, as they matched an unusual double colon pattern. The researchers found that the code converts these double colons into path separators, which defeats the checks meant to stop directory traversal. A deprecated function that is still active then uses the resulting path to read local files.
In Jira, watchTowr says this let them reach the web.xml configuration file, which is normally protected by several mechanisms in Jira and Tomcat. They could not traverse outside the Tomcat context, but could read any file within the application server. They report that the route varies across the other products but works in much the same way. In Bitbucket, web.xml is blocked, so the details differ slightly.
Why it matters
Anyone running self-hosted Atlassian tools is exposed, and because the flaw sits in a shared library, one weakness spans several products at once. It breaks the assumption that path filtering and protected configuration files keep sensitive content out of reach, since the double colon pattern slipped past checks written for slashes and dots. It also means WAF rules are a stopgap at best, so teams cannot rely on them in place of patching.
What to do
- Apply the patched versions listed in Atlassian's CVE-2026-21589 advisory to every on-premises Jira, Confluence and Bitbucket instance.
- Inventory all self-hosted Atlassian products, including forgotten or test instances exposed to the internet.
- Add WAF rules that block double colon (::) sequences in request paths, as Atlassian suggests, until patching is complete.
- Review web server logs for requests to /download/resources/ paths containing double colon patterns.