Frappe ERPNext unauthorized voucher changes in bank reconciliation
Affects Frappe ERPNext 13.0.0 before 15.122.0 and 16.x before 16.50.0, for users with the Accounts User role who can edit a Bank Transaction. Fixed in 15.122.0 and 16.50.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 15.122.0, 16.50.0
- Who is exposed
- Specific setups only
Summary
Written by a model
Frappe ERPNext 13.0.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in an Accounts module endpoint that reconciles Bank Transactions against caller-named vouchers, checking permission only on the Bank Transaction and not on each voucher. Authenticated users with the Accounts User role who can edit a Bank Transaction can send crafted requests naming vouchers outside their permitted scope to change the reconciliation state of vouchers belonging to other companies or outside their User Permissions.
Who should check
Teams running Frappe ERPNext 13.0.0 through 15.x before 15.122.0, or 16.x before 16.50.0, where Accounts users handle bank reconciliation
“Frappe ERPNext 13.0.0 before 15.122.0 and 16.x before 16.50.0”
What to do
Check whether your setup matches what the bug needs.
Frappe ERPNext versions 13.0.0 before 15.122.0 or 16.x before 16.50.0 User must have the Accounts User role and be able to edit a Bank TransactionUpgrade to a fixed version: 15.122.0, 16.50.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134396 (Frappe ERPNext 13.0.0 before 15.122.0 Missing Authorization in Bank Reconciliation), 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-134396 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 13.0.0, fixed in 15.122.0
- frappe erpnext: from 16.0.0, fixed in 16.50.0
Fixed versions: 15.122.0, 16.50.0.
Conditions (all must be true for the bug to be hit):
- Frappe ERPNext versions 13.0.0 before 15.122.0 or 16.x before 16.50.0 (source: https://www.vulncheck.com/advisories/frappe-erpnext-13.0.0-before-15.122.0-missing-authorization-in-bank-reconciliation)
- User must have the Accounts User role and be able to edit a Bank Transaction (source: https://www.vulncheck.com/advisories/frappe-erpnext-13.0.0-before-15.122.0-missing-authorization-in-bank-reconciliation)
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-134396 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134396 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-9jx6-f65v-r6h7
- https://www.vulncheck.com/advisories/frappe-erpnext-13.0.0-before-15.122.0-missing-authorization-in-bank-reconciliation
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-134396
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-134396"}.Affected versions
- frappe erpnextFrom 13.0.0 · fixed in 15.122.0
- frappe erpnextFrom 16.0.0 · fixed in 16.50.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 20 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · frappe/erpnext · Advisory GHSA-9jx6-f65v-r6h7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134396 |
| Record | NVD · CVE-2026-134396 |
| Other links 1 | |
| Link | vulncheck.com · advisories/frappe-erpnext-13.0.0-before-15.122.0-missing-authorization-in-bank-reconciliation |
Questions about CVE-2026-134396
Is CVE-2026-134396 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: cve.now feed data
What does this mean?
An authenticated user can change the reconciliation state of vouchers that belong to other companies or fall outside their User Permissions.
Source: vulncheck.com
Which versions are affected by CVE-2026-134396?
erpnext: from 13.0.0 before 15.122.0. erpnext: from 16.0.0 before 16.50.0.
Source: cve.now feed data
Am I affected, and how do I check?
Frappe ERPNext versions 13.0.0 before 15.122.0 and 16.x before 16.50.0 are in scope. The condition is an authenticated user with the Accounts User role who can edit a Bank Transaction, so check the installed ERPNext version and which users hold that role.
Source: vulncheck.com
How do I fix CVE-2026-134396?
Upgrade to ERPNext 15.122.0 or 16.50.0, the fixed versions for the affected branches.
Source: vulncheck.com
Related
- CVE-2026-134389Frappe ERPNext 6.18.0 before 15.124.0 Unauthorized Document Access via Payment Requests
- CVE-2026-134372Frappe ERPNext 4.3.0 before 15.121.6 SQL Injection in Selling and Buying Modules
- CVE-2026-134378Frappe ERPNext 12.7.0 before 15.124.0 Information Disclosure via Public Supplier E-Invoice Files
- CVE-2026-134373Frappe ERPNext 14.0.0 before 15.121.0 Missing Authorization in Bulk Transaction Retry
- CVE-2026-134374Frappe ERPNext 15.0.0 before 15.124.0 Missing Authorization in Assets Depreciation Endpoints
- CVE-2026-134375Frappe ERPNext 13.0.0 before 15.124.0 Missing Authorization in Accounts Payment Entries
No corrections so far. Something wrong on this page? Report an error.