# CVE-2021-26085: Atlassian Confluence Server Pre-Authorization Arbitrary File Read

> Remote attackers can view restricted resources via an arbitrary file read vulnerability in the /s/ endpoint of Atlassian Confluence Server.

- **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 28 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2021
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-8mjc-qhq2-3xm8

## What is CVE-2021-26085?

CVE-2021-26085 is a medium-severity path traversal vulnerability in Atlassian Confluence Data Center, published on 3 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 Confluence Server allow remote attackers to view restricted resources via a Pre-Authorization Arbitrary File Read vulnerability in the /s/ endpoint. The affected versions are before version 7.4.10, and from version 7.5.0 before 7.12.3.

Weakness: CWE-425 (Direct Request)

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

It affects 2 products.


Products: Atlassian Confluence Data Center, Atlassian Confluence Server.

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

No fix has been published for CVE-2021-26085 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Apr 2022.

## Is CVE-2021-26085 being exploited?

Yes. Attackers have exploited CVE-2021-26085 in the wild since at least 28 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Atlassian Confluence Server 7.5.1 Pre-Authorization Arbitrary File Read vulnerability (CVE-2021-26085) (github_poc): https://github.com/ColdFusionX/CVE-2021-26085
- Atlassian Confluence 7.12.2 - Pre-Authorization Arbitrary File Read (exploitdb)
- Atlassian Confluence Server - Local File Inclusion (nuclei): http/cves/2021/CVE-2021-26085.yaml

## Other vulnerabilities in Atlassian Confluence Data Center

- [CVE-2023-22527](https://insights.sbomify.com/CVE-2023-22527/): Atlassian Confluence Data Center and Server Template Injection (critical 10.0, exploited in the wild)
- [CVE-2023-22518](https://insights.sbomify.com/CVE-2023-22518/): Atlassian Confluence Data Center and Server Improper Authorization (critical 10.0, exploited in the wild)
- [CVE-2023-22515](https://insights.sbomify.com/CVE-2023-22515/): Atlassian Confluence Data Center and Server Broken Access Control (critical 10.0, exploited in the wild)
- [CVE-2022-26134](https://insights.sbomify.com/CVE-2022-26134/): Atlassian Confluence Server and Data Center Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-26084](https://insights.sbomify.com/CVE-2021-26084/): Atlassian Confluence Server and Data Center Object-Graph Navigation Language (OGNL) Injection (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-26085 is a medium-severity path traversal vulnerability in Atlassian Confluence Data Center, published on 3 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-26085 in the wild since at least 28 Mar 2022, including in ransomware campaigns.

Affected product: Atlassian Confluence 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-26085/ (Markdown: https://insights.sbomify.com/CVE-2021-26085/index.md)
```

## Sources

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

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