CVE
Atlassian Jira Software Data Center path traversal in file serving allows arbitrary file reads
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
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Do first: Workaround: The checked facts do not include a workaround or mitigation. The Atlassian advisory is the source to check for one.
- 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? →
- 34/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? →
- Unclear
- 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: yes
- Technical impact: partial
Summary
A path traversal flaw in Atlassian's Jira Software Data Center lets an attacker read protected resources outside the directories the software is meant to serve. An attacker can exploit it remotely over the network, without logging in and without any action from a user.
Written by a model from the sources below. Verify against them.
Original description
This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21606 was introduced in versions 10.3.26 and 11.3.12.
This Path Traversal (Arbitrary Read/Write) vulnerability, with a CVSS Score of 8.7 and a CVSS Vector of 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 allows an unauthenticated attacker to disclose protected resources outside declared resource directories, which has high impact to confidentiality, no impact to integrity, no impact to availability, and requires no user interaction.
Atlassian recommends that Jira Software Data Center customers upgrade to the latest version. If you are unable to do so, upgrade your instance to one of the specified supported fixed versions:
Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27
See the release notes (https://confluence.atlassian.com/jirasoftware/jira-software-data-center-release-notes.html). You can download the latest version of Jira Software Data Center from the Jira Data Center Download Archives (https://www.atlassian.com/software/jira/download-archives).
Who should check
Teams running Atlassian Jira Software Data Center 10.3.26 or 11.3.12 (the versions where this bug was introduced)
“was introduced in versions 10.3.26 and 11.3.12”
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 39 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts do not include a workaround or mitigation. The Atlassian advisory is the source to check for one.
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-21606 (This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21606 was introduced in versions 10.3.26 and…), 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-21606 (entry last updated 2026-11-17):
Affected:
- Atlassian Jira Software Data Center: versions 11.3.12, 10.3.26
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Jira Software Data Center versions 10.3.26 and 11.3.12 (source: https://jira.atlassian.com/browse/JSWSERVER-27106)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-21606 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-21606 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/JSWSERVER-27106
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-21606
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-21606"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Atlassian Jira Software Data Center
11.3.12, 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-21606
Is CVE-2026-21606 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 unauthenticated attacker can read protected resources outside the declared resource directories in Jira Software Data Center. The impact is high confidentiality loss, with no integrity or availability impact.Source: jira.atlassian.com
Which versions are affected by CVE-2026-21606?
Jira Software Data Center: versions 11.3.12, 10.3.26.Source: cve.now feed data
Am I affected, and how do I check?
The bug was introduced in Jira Software Data Center versions 10.3.26 and 11.3.12. Readers can compare the installed Jira Software Data Center version against those two versions.Source: jira.atlassian.com
How do I fix CVE-2026-21606?
The checked facts do not name a fixed version or vendor patch, so no upgrade target can be given. The Atlassian advisory is the source to check for a fix.Source: jira.atlassian.com
What if there's no patch?
The checked facts do not include a workaround or mitigation. The Atlassian advisory is the source to check for one.Source: jira.atlassian.com