Skip to content
TrustList
Security advisories

Jira Service Management Data Center fixes high-severity access flaw

Editorial

By TrustList Editorial

CVE-2026-21609 (CVSS 7.1) lets a logged-in user reach resources they should not, and possibly run code; fixed in 10.3.27 and 11.3.13 of the self-managed edition.

About Jira Service Management Data Center fixes high-severity access flaw

Jira Service Management Data Center fixes high-severity access flaw

17 November 2026: Atlassian has fixed CVE-2026-21609, a high-severity improper authorization flaw (CVSS 7.1) in Jira Service Management Data Center that lets an authenticated attacker reach resources or functions they should not, and could expose sensitive information or allow code to be run. The fixes are in 10.3.27 and 11.3.13. Atlassian does not report any exploitation, and the flaw came in through its bug bounty programme.

Not yet independently verified. Atlassian's public ticket gives the fixed versions but no publication date, and Atlassian has not said whether Jira Service Management Server 5.12 has a fix. Canada's Cyber Centre lists Server 5.12.16 to 5.12.42 as affected. We will update this when it can be confirmed, and remove this note.

Versions to move to

The flaw was introduced in 5.12.0, 10.3.0 and 11.3.0, and Atlassian's ticket lists every feature release from 5.12 through 11.3 as affected. Its advice is to upgrade to the latest release, or at least to:

  • 10.3.27 or later on the 10.3 long-term support line;
  • 11.3.13 or later on the 11.3 line.

Canada's Cyber Centre, in advisory AV26-1166 of 17 November, also lists Jira Service Management Server 5.12.16 to 5.12.42 as affected. Atlassian's ticket names no fix for the Server line.

The ticket describes the impact only in broad terms: unintended access that can expose resources or functionality, possibly giving an attacker sensitive information or even letting them execute arbitrary code. It does not say which endpoint or permission check is at fault, and it names no workaround, so upgrading is the only remedy it offers. Atlassian puts moving to the latest release first, with the two fixed builds as the minimum for customers who cannot go that far.

A flaw that needs a login, on a system full of logins

Because the attacker must be signed in, the realistic risk is from accounts that already exist: agents, portal customers on instances that allow self sign-up, and integration users. Service desks open to external customers are the ones where an unknown person can most easily get an account. Atlassian Cloud is not named in the ticket.

The ticket was created on 13 November and marked fixed on 17 November. It lists the affected feature releases as 5.12, 5.15, 5.16 and 5.17, every release from 10.0 to 10.7, and 11.0 to 11.3, and points to the release notes and the download archive for the fixed builds.

The rest of this week's Atlassian picture

The same week brought Java4Shell, a critical OpenJDK flaw that its finders showed reaching remote code execution in Jira and Confluence before login on some x86-64 servers. Self-managed Atlassian sites running on an affected JDK need both the application update and a Java update.

Atlassian is in our catalogue, and our service desk software category lists 17 products.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in

The quantum software company, founded in 2017 with offices from Sydney to Oxford, says the round, A$415 million, was expanded twice and brings in AMD Ventures, EDGE Group and Australia's National Reconstruction Fund for its GPS-free navigation push.