Skip to main content
VulnerabilityPublished

CVE-2026-21601: Atlassian Jira Service Management Data Center · Broken Authentication & Session Management

Affects Atlassian Jira Service Management Data CenterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 17 Nov 2026, 18:21 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (atlassian)CVSS 4.08.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
AtlassianJira Service Management Data CenterAffected
  • 10.2.0 to 10.2.1 – 11.2.0 to 11.2.1
8 affected builds
Fixed in–

AI-suggested

Atlassian recommends upgrading affected Jira Service Management Data Center instances to version 10.3.27 or later if using the 10.3 series, or to version 11.3.13 or later if using the 11.3 series. Applying these official fixes will remediate the vulnerability. No alternative mitigations or temporary workarounds are indicated.

Description

CVE-2026-21601 is a high severity Broken Authentication and Session Management (BASM) vulnerability in Atlassian Jira Service Management Data Center versions 10.0.0 and 11.0.0. It allows an unauthenticated attacker to perform actions as another user. Atlassian recommends upgrading to fixed versions 10.3.27 or later in the 10.3 series, or 11.3.13 or later in the 11.3 series to remediate this issue.

References

Community reviews

Loading reviews…