CVE
Atlassian Jira Service Management Data Center authorization bypass enabling unintended access
Affects Jira Service Management Data Center from 5.12.0 to 11.3.0. Fixed by upgrading the 10.3 line to 10.3.27 or later.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 10.3.27
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Jira Service Management Data Center versions introduced with this bug: 5.12.0, 10.3.0 and 11.3.0 (affected range per the advisory's affects list runs from 5.12.0 to 11.3.0).
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.48% · 42nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Atlassian's Jira Service Management Data Center and Server contain an improper authorization flaw. An attacker with a low-privilege login can reach it over the network and gain unintended access to resources or functionality, which could expose sensitive information or, in some cases, allow arbitrary code execution.
Original description
This High severity Improper Authorization vulnerability was introduced in versions 5.12.0, 10.3.0, and 11.3.0 of Jira Service Management Data Center. This Improper Authorization vulnerability, with a CVSS Score of 7.1, allows an authenticated attacker to gain unintended access and can lead to the exposure of resources or functionality, possibly providing attackers with sensitive information or even execute arbitrary code. Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can download the latest version of Jira Service Management Data Center from the download center (https://www.atlassian.com/software/jira/service-management/download-archives). This vulnerability was reported via our Bug Bounty program.
Who should check
Teams running Jira Service Management Data Center from 5.12.0 through 11.3.x, including the 10.3.x and 11.3.x branches, and anyone on Jira Service Management Server listed as affected.
“introduced in versions 5.12.0, 10.3.0, and 11.3.0 of Jira Service Management Data Center”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Jira Service Management Data Center versions introduced with this bug: 5.12.0, 10.3.0 and 11.3.0 (affected range per the advisory's affects list runs from 5.12.0 to 11.3.0).Upgrade to a fixed version: 10.3.27.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-21609 (This High severity Improper Authorization vulnerability was introduced in versions 5.12.0, 10.3.0, and 11.3.0 of Jira Service Management…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-21609 (entry last updated 2026-11-17):
Affected:
- Atlassian Jira Service Management Data Center: versions 11.3.0 to 11.3.12, 11.2.0 to 11.2.1, 11.1.0 to 11.1.1, 11.0.0 to 11.0.1, 10.7.1 to 10.7.4, 10.6.0 to 10.6.1, 10.5.0 to 10.5.1, 10.4.0 to 10.4.1, 10.3.0 to 10.3.26, 10.2.0 to 10.2.1, 5.17.5, 5.12.16 to 5.12.42
- Atlassian Jira Service Management Server: versions 5.12.16 to 5.12.42
Fixed versions: 10.3.27.
Conditions (all must be true for the bug to be hit):
- Jira Service Management Data Center versions introduced with this bug: 5.12.0, 10.3.0 and 11.3.0 (affected range per the advisory's affects list runs from 5.12.0 to 11.3.0). (source: https://jira.atlassian.com/browse/JSDSERVER-16936)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-21609 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21609 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://confluence.atlassian.com/pages/viewpage.action?pageId=1874690748
- https://jira.atlassian.com/browse/JSDSERVER-16936
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-21609
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-21609"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Atlassian Jira Service Management Data Center
11.3.0 to 11.3.12, 11.2.0 to 11.2.1, 11.1.0 to 11.1.1, 11.0.0 to 11.0.1, 10.7.1 to 10.7.4, 10.6.0 to 10.6.1, 10.5.0 to 10.5.1, 10.4.0 to 10.4.1, 10.3.0 to 10.3.26, 10.2.0 to 10.2.1, 5.17.5, 5.12.16 to 5.12.42
- Atlassian Jira Service Management Server
5.12.16 to 5.12.42
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Link
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-21609
Is CVE-2026-21609 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated attacker can gain access they are not meant to have, which can expose resources or functionality, possibly including sensitive information.Source: jira.atlassian.com
Which versions are affected by CVE-2026-21609?
Jira Service Management Data Center: versions 11.3.0 to 11.3.12, 11.2.0 to 11.2.1, 11.1.0 to 11.1.1, 11.0.0 to 11.0.1, 10.7.1 to 10.7.4 and 7 more. Jira Service Management Server: version 5.12.16 to 5.12.42.Source: cve.now feed data
Am I affected, and how do I check?
The bug was introduced in Jira Service Management Data Center versions 5.12.0, 10.3.0 and 11.3.0, and the advisory's affects list runs from 5.12.0 to 11.3.0. Compare the installed Data Center version against that range.Source: jira.atlassian.com
How do I fix CVE-2026-21609?
Upgrade Jira Service Management Data Center 10.3 to 10.3.27 or a later release, as the advisory directs.Source: jira.atlassian.com