Skip to content
Noroxi
CVE-2021-26086· NVD / CVE Program· CNA atlassian

Affected versions of Atlassian Jira Server and Data Center allow remote attackers to read particular files via a path traversal vulnerabilit

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.

MediumCVSS 5.3 · v3.1KEVWeaponized No fix recorded
Published
Aug 15, 2021
Updated
Jun 16, 2026
EPSS
100.0% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

81

Now

Patch today or shut off access.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
30 / 30 · Listed
EPSS
30 / 30 · 100.0%

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 government agencies: Dec 3, 2024.

Affected systems

VendorProduct
atlassianjira data center
atlassianjira server

Affected versions

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

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

Other 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 reques
    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 b
    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 si
    47Plan
  • CVE-2022-36801Affected versions of Atlassian Jira Server and Data Center allow anonymous remote attackers to inject arbitrary HTML or JavaScript via a Ref
    44Plan
  • CVE-2020-14179Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom SLA
    44Plan
  • CVE-2022-36799This issue exists to document that a security improvement in the way that Jira Server and Data Center use templates has been implemented.
    41Plan

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.

Public exploit evidence
SourceKindDate
Exploit-DB entrywebapps2021-10-06
Nuclei detection templateNuclei template CVE-2021-26086 —
Proof-of-concept repository on GitHubstars:02021-09-05
Proof-of-concept repository on GitHubstars:252021-10-05
Proof-of-concept repository on GitHubstars:02021-11-16

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.

  1. Published
  2. First PoC+20 d
  3. CISA KEV+1184 d
  4. TodaySep 29, 2026+1871 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

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

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records