Skip to main content
VulnerabilityPublished

CVE-2026-21602: Atlassian Jira Core Data Center · Stored XSS

Affects Atlassian Jira Core Data CenterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High.

Data as of 17 Nov 2026, 18:21 UTC

CVSS 4.0 base score
7.4High
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.07.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/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 Core Data CenterAffected
  • =10.3.26
Fixed in–
AtlassianJira Software Data CenterAffected
  • =10.3.26
Fixed in–

AI-suggested

Atlassian recommends upgrading affected Jira Core Data Center and Jira Software Data Center instances from version 10.3.26 to at least 10.3.27 or 11.3.13 depending on the release line. Applying these official fixes fully mitigates the vulnerability. No other mitigation or workaround is specified by the vendor.

Description

CVE-2026-21602 is a high severity Stored Cross-Site Scripting (XSS) vulnerability affecting Atlassian Jira Core Data Center and Jira Software Data Center version 10.3.26. It allows an authenticated attacker to execute arbitrary HTML or JavaScript code in the context of a victim's browser. Atlassian recommends upgrading to fixed versions 10.3.27 or later for the 10.3 release line, or 11.3.13 or later for the 11.3 release line to remediate this issue.

References

Community reviews

Loading reviews…