# CVE-2021-26086: Atlassian Jira Server and Data Center Path Traversal

> Remote attackers can read sensitive files via a path traversal vulnerability in the web.xml endpoint of Atlassian Jira Server and Data Center.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 12 Nov 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2021
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-vvhj-8w7x-qj58

## What is CVE-2021-26086?

CVE-2021-26086 is a medium-severity path traversal vulnerability in Atlassian Jira Data Center, published on 16 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-26086?

It affects 2 products.


Products: Atlassian Jira Data Center, Atlassian Jira Server.

## How do I fix CVE-2021-26086?

No fix has been published for CVE-2021-26086 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Dec 2024.

## Is CVE-2021-26086 being exploited?

Yes. Attackers have exploited CVE-2021-26086 in the wild since at least 12 Nov 2024.

Public exploit code:

- Atlassian Jira Server/Data Center 8.4.0 - Arbitrary File read (CVE-2021-26086) (github_poc): https://github.com/ColdFusionX/CVE-2021-26086
- Confluence OGNL Injection [CVE-2021-26084]. (github_poc): https://github.com/Jeromeyoung/CVE-2021-26086
- Atlassian Jira Server Data Center 8.16.0 - Arbitrary File Read (exploitdb)
- Confluence server webwork OGNL injection (github_poc): https://github.com/Official-BlackHat13/CVE-2021-26086
- Atlassian Jira Limited - Local File Inclusion (nuclei): http/cves/2021/CVE-2021-26086.yaml

## Other vulnerabilities in Atlassian Jira Data Center

- [CVE-2022-0540](https://insights.sbomify.com/CVE-2022-0540/): Auth bypass in Jira Core Server (critical 9.8)
- [CVE-2020-36239](https://insights.sbomify.com/CVE-2020-36239/): Deserialization in Jira Core Data Center (critical 9.8)
- [CVE-2025-22167](https://insights.sbomify.com/CVE-2025-22167/): Path traversal in Jira Software Data Center (high 8.7)
- [CVE-2019-20419](https://insights.sbomify.com/CVE-2019-20419/): Other in Jira Server (high 7.8)
- [CVE-2024-21685](https://insights.sbomify.com/CVE-2024-21685/): Information disclosure in Jira Core Data Center (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26086 and fix it if it is affected.

What it is: CVE-2021-26086 is a medium-severity path traversal vulnerability in Atlassian Jira Data Center, published on 16 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-26086 in the wild since at least 12 Nov 2024.

Affected product: Atlassian Jira Data Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-26086/ (Markdown: https://insights.sbomify.com/CVE-2021-26086/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-26086
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-26086
- OSV: https://osv.dev/vulnerability/CVE-2021-26086

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-26086/
Summaries are generated and may contain mistakes; the official description above is the record.