# CVE-2026-39352: Frappe has an Arbitrary File Read via Path Traversal in render_include

> Attackers can read arbitrary files from the server via path traversal in the render_include function of the Frappe framework.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2026
- **Updated:** 21 May 2026
- **Also known as:** GHSA-67rf-pxgh-vfqv

## What is CVE-2026-39352?

CVE-2026-39352 is a high-severity path traversal vulnerability in frappe, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Frappe is a full-stack web application framework. Versions prior to 15.105.0 and 16.15.0 contain a possible Arbitrary File Read vulnerability via Path Traversal. The issue is resolved in versions 16.15.0, 15.105.0 and above.

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

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


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

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

## Is CVE-2026-39352 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39352 exists.

Public exploit code:

- Frappe Framework < 16.15.0 - Arbitrary File Read via render_include Path Traversal (nuclei): http/cves/2026/CVE-2026-39352.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39352 is a high-severity path traversal vulnerability in frappe, published on 20 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39352 exists.

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

## Sources

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

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