This High severity Path Traversal (Arbitrary Read/Write) vulnerability known as CVE-2026-21606 was introduced in
Source GCVE Database
Not known to be exploited · CVSS 8.7 High.
Data as of 17 Nov 2026, 19:51 UTC
Thin evidence
One scorer or none| CNA (atlassian) | CVSS 4.0 | 8.7 |
|---|
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/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 Software Data Center | Affected
| Fixed in– |
Mavencom.atlassian.jira/jira-software-data-centerpkg:maven/com.atlassian.jira/jira-software-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 Jira Software Data Center to version 11.3.13 or later if using the 11.3 series, or to version 10.3.27 or later if using the 10.3 series. These versions contain the official fixes for this vulnerability. No other mitigation steps are indicated.
Description
CVE-2026-21606 is a high severity path traversal vulnerability affecting Jira Software Data Center versions 10.3.26 and 11.3.12. It allows an unauthenticated attacker to read protected resources outside the intended directories, impacting confidentiality without affecting integrity or availability. No user interaction is required for exploitation. Atlassian recommends upgrading to versions 11.3.13 or later for the 11.3 series, and 10.3.27 or later for the 10.3 series to remediate this issue.