CVE
Atlassian Jira Core Data Center script injection via stored XSS in web interface
Affects Jira Core Data Center and Jira Software Data Center 10.3.26, where the flaw was introduced. Fixed in 10.3.27.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/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. Running Jira Core Data Center or Jira Software Data Center version 10.3.26
- 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
- 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? →
- 16/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 Core Data Center and Jira Software Data Center contain a stored cross-site scripting flaw that lets a remote attacker with a low-privilege login run arbitrary HTML or JavaScript in a victim's browser. The attack requires a user to take some action before the code runs.
Original description
This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center.
This Stored XSS vulnerability, with a CVSS Score of 8.4, allows an authenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser.
Atlassian recommends that Jira Core Data Center and Jira Software 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 Core Data Center and Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27
- Jira Core Data Center and Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13
See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Core Data Center and Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives).
This vulnerability was reported via our Penetration Testing program.
Who should check
Teams running Jira Core Data Center or Jira Software Data Center 10.3.26
“introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Running Jira Core Data Center or Jira Software Data Center version 10.3.26Upgrade 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-21603 (This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center.), 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-21603 (entry last updated 2026-11-17):
Affected:
- Atlassian Jira Core Data Center: versions 10.3.26
- Atlassian Jira Software Data Center: versions 10.3.26
Fixed versions: 10.3.27.
Conditions (all must be true for the bug to be hit):
- Running Jira Core Data Center or Jira Software Data Center version 10.3.26 (source: https://jira.atlassian.com/browse/JRASERVER-79585)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-21603 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21603 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/JRASERVER-79585
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-21603
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-21603"}.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 Core Data Center
10.3.26
- Atlassian Jira Software Data Center
10.3.26
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-21603
Is CVE-2026-21603 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 get arbitrary HTML or JavaScript code to run in a victim's browser through this stored cross-site scripting flaw.Source: jira.atlassian.com
Which versions are affected by CVE-2026-21603?
Jira Core Data Center: version 10.3.26. Jira Software Data Center: version 10.3.26.Source: cve.now feed data
Am I affected, and how do I check?
The flaw was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center. Check the installed version of either product to see which release it is running.Source: jira.atlassian.com
How do I fix CVE-2026-21603?
Upgrade to 10.3.27 or a later release, as Atlassian advises for Jira Core Data Center and Jira Software Data Center 10.3.Source: jira.atlassian.com