# CVE-2026-47182: Frappe: Broken Access Control on Private Files

> Authenticated users can access private files by guessing paths, allowing unauthorized data disclosure in the Frappe framework.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-gvg7-4p32-j648

## What is CVE-2026-47182?

CVE-2026-47182 is a medium-severity missing authorization vulnerability in frappe, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frappe is a full-stack web application framework. Prior to version 16.17.4, any authenticated user can access private files by guessing the file path. This issue has been patched in version 16.17.4.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-47182?


## How do I fix CVE-2026-47182?

No fix has been published for CVE-2026-47182 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47182 being exploited?

There is no known exploitation of CVE-2026-47182 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47182 and fix it if it is affected.

What it is: CVE-2026-47182 is a medium-severity missing authorization vulnerability in frappe, published on 12 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47182 in the wild and no public exploit code.

Affected product: frappe. 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-2026-47182/ (Markdown: https://insights.sbomify.com/CVE-2026-47182/index.md)
```

## Sources

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

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