CVE-2021-26086: Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal…
Noroxi assessment
Priority: Now (action score 81/100)
- CISA has confirmed exploitation in the wild (Nov 12, 2024). Remediation deadline for US federal agencies: Dec 3, 2024.
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 99.9% (FIRST EPSS); higher than 99.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Patch today or shut off access. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal vulnerability in the /WEB-INF/web.xml endpoint. The affected versions are before version 8.5.14, from version 8.6.0 before 8.13.6, and from version 8.14.0 before 8.16.1.
- Published
- Aug 15, 2021
- Updated
- Jun 16, 2026
- EPSS
- 99.9% · 99th percentile
- CWE
- CWE-22
Report tools
Action score
81
Patch today or shut off access.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 30 / 30 · 99.9%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Nov 12, 2024. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Dec 3, 2024.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| atlassian | jira data center | cpe:2.3:a:atlassian:jira_data_center |
| atlassian | jira server | cpe:2.3:a:atlassian:jira_server |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (atlassian). Independent of NVD's CPE analysis and usually ahead of it.
Atlassian Jira Data Center
- unspecified and later · before 8.5.14affected
- 8.6.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.6affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.16.1affected
Atlassian Jira Server
- unspecified and later · before 8.5.14affected
- 8.6.0 and later · before unspecifiedaffected
- unspecified and later · before 8.13.6affected
- 8.14.0 and later · before unspecifiedaffected
- unspecified and later · before 8.16.1affected
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- atlassian jira data centerbefore 8.5.14
- atlassian jira data center8.6.0 and later · before 8.13.6
- atlassian jira data center8.14.0 and later · before 8.16.1
- atlassian jira serverbefore 8.5.14
- atlassian jira server8.6.0 and later · before 8.13.6
- atlassian jira server8.14.0 and later · before 8.16.1
Same product
atlassian: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0540A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP…65This week
- CVE-2020-36239Jira Data Center, Jira Core Data Center, Jira Software Data Center from version 6.3.0 before 8.5.16, from 8.6.0 before 8.13.8, from 8.14.0…54Plan
- CVE-2022-26135A vulnerability in Mobile Plugin for Jira Data Center and Server allows a remote, authenticated user (including a user who joined via the…47Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-14179Sep 20, 2020 · Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom…44Plan
- ← EarlierCVE-2021-26080Jun 7, 2021 · EditworkflowScheme.jspa in Jira Server and Jira Data Center before version 8.5.14, and from version 8.6.0 before version 8.13.6, and from 8.24Monitor
- Later →CVE-2021-39116Sep 7, 2021 · Affected versions of Atlassian Jira Server and Data Center allow remote attackers to impact the application's availability via a Denial of…22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Exploit-DB entry ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×3
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 3 repositories | 2021-09-05 → 2021-11-16 |
| Exploit-DB entry | webapps | 2021-10-06 |
| Nuclei detection template | Nuclei template CVE-2021-26086 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+20 d
- CISA KEV+1184 d
- TodayNov 14, 2026+1916 d
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0841 · Oct 15, 2021( Jira Server Güvenlik Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.