CVE-2026-21603: This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data
Source GCVE Database
Not known to be exploited · CVSS 8.4 High.
Data as of 17 Nov 2026, 19:50 UTC
Thin evidence
One scorer or none| CNA (atlassian) | CVSS 4.0 | 8.4 |
|---|
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| AtlassianJira Core Data Center | Affected
| Fixed in– |
| AtlassianJira Software Data Center | Affected
| Fixed in– |
Mavencom.atlassian.jira/jira-core-data-centerpkg:maven/com.atlassian.jira/jira-core-data-centerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Atlassian recommends upgrading affected Jira Core Data Center and Jira Software Data Center instances to version 10.3.27 or later for the 10.3.x series, or 11.3.13 or later for the 11.3.x series. Applying these official fixes fully mitigates the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
A high severity Stored Cross-Site Scripting (XSS) vulnerability (CVE-2026-21603) affects Jira Core Data Center and Jira Software Data Center starting from version 10.3.26. This vulnerability allows an authenticated attacker to execute arbitrary HTML or JavaScript code in the victim's browser. Atlassian recommends upgrading to fixed versions 10.3.27 or later for the 10.3.x line, or 11.3.13 or later for the 11.3.x line to remediate this issue.