Skip to content

WebHigh 8.4Patch available

CVE-2026-21603

Stored XSS in Jira Data Center allows authenticated attackers to run JS in users' browsers.

How scary is it?

updated 18 Nov 2026
  • No

    Works without logging in1

    Needs a login: a basic user account (CVSS PR:L).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 2 products in an affected versionAtlassian Jira Core Data Center / Atlassian Jira Software Data Center

    Atlassian Jira Core Data Center: 10.3.26

    Atlassian Jira Software Data Center: 10.3.26

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. The attacker has a user account

    CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.

    Source 1

  4. A person takes an action, such as opening a link or a file

    CVSS user interaction: required (UI:A). A victim must click, open or otherwise cooperate.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release11.3.13 / 10.3.27

    Atlassian Jira Core Data Center: 11.3.13, 10.3.27

    Atlassian Jira Software Data Center: 11.3.13, 10.3.27

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenUpgrade to >=10.3.27 or >=11.3.13; restrict access and review logs until patched.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Affects widely used enterprise product (Atlassian Jira Data Center). Vulnerability can enable session theft/account compromise across organizations; broad upgrade advised.

CVSS
8.4Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.33%chance of exploitation in the next 30 daystop 74% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in 11.3.13, 10.3.27per the vendor
Published
17 Nov 2026analysed here 18 Nov 2026

Do first. Upgrade to a fixed release: 11.3.13, 10.3.27.

Summary

Impact

Authenticated attacker can store and execute arbitrary HTML/JS in victims' browsers, enabling session theft, account takeover, phishing or data exfiltration.

Triage

Attack surface
Client-side
Exploitable
At runtime
Attack vector
network
Weakness
  • CWE-79 Cross-Site Scripting (XSS)
Can a WAF block it?
Yes. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Atlassian Jira Core Data Center10.3.26Vendor says fixed in: 11.3.13, 10.3.27
Atlassian Jira Software Data Center10.3.26Vendor says fixed in: 11.3.13, 10.3.27

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Jira Core Data Center 10.3.26
  • Jira Software Data Center 10.3.26
  • Jira Data Center releases <10.3.27 and <11.3.13

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? Yes. Cross-site scripting sends script tags or event handlers in the request, which WAF signatures match well.

Also consider: CSP · output encoding

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable no, technical impact partialAssessed by CISA 17 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 17 Nov 2026Published
  2. 17 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 17 Nov 2026CVE record last updatedsame day later
  4. 18 Nov 2026Analysed by vulneraibility.com1 day later

Common questions

Is CVE-2026-21603 being exploited?

Not confirmed. CVE-2026-21603 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-21603?

CVE-2026-21603 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-21603?

Yes. A fix has been recorded for CVE-2026-21603. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-21603 affect?

CVE-2026-21603 affects Jira Core Data Center 10.3.26, Jira Software Data Center 10.3.26, Jira Data Center releases <10.3.27 and <11.3.13. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-21603?

Upgrade to >=10.3.27 or >=11.3.13; restrict access and review logs until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

2 references in the CVE record, grouped by the tags the record gives them.

Other links (2)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.