Skip to main content
Menu
CVEs

Frappe ERPNext authorization bypass exposes supplier portal records

Only affects ERPNext 15.94.2 before 15.122.0 and 16.x before 16.50.0 where a Customer and a Supplier share a name. Fixed in 15.122.0 and 16.50.0.

CVE-2026-134406Published November 21, 2026, updated

2.3LowCNA
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 15.94.2 before 15.122.0 and 16.x before 16.50.0 contains an incorrect authorization vulnerability in a supplier portal endpoint whose party identity check ignores party type, failing to distinguish a Customer and a Supplier that share a name. Authenticated users, including portal users or users with no assigned roles, can send crafted requests naming records outside their permitted scope to read buying-portal records.

Who should check

Teams running ERPNext 15.94.2 through 15.x before 15.122.0, or 16.x before 16.50.0, with supplier portal users or accounts that have no assigned roles.

“Frappe ERPNext 15.94.2 before 15.122.0 and 16.x before 16.50.0”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Affects ERPNext 15.94.2 before 15.122.0 and 16.x before 16.50.0 A Customer and a Supplier share the same name (party name collision)
  2. Upgrade 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-134406 (ERPNext 15.94.2 before 15.122.0 Unauthorized Supplier Portal Record Access via Party Name Collision), 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-134406 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 15.94.2, 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):
- Affects ERPNext 15.94.2 before 15.122.0 and 16.x before 16.50.0 (source: https://www.vulncheck.com/advisories/erpnext-15.94.2-before-15.122.0-unauthorized-supplier-portal-record-access-via-party-name-collision)
- A Customer and a Supplier share the same name (party name collision) (source: https://www.vulncheck.com/advisories/erpnext-15.94.2-before-15.122.0-unauthorized-supplier-portal-record-access-via-party-name-collision)
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-134406 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134406 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-xmw8-rg38-x88j
- https://www.vulncheck.com/advisories/erpnext-15.94.2-before-15.122.0-unauthorized-supplier-portal-record-access-via-party-name-collision
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-134406
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-134406"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 17 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · frappe/erpnext · Advisory GHSA-xmw8-rg38-x88j
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134406
RecordNVD · CVE-2026-134406
Other links 1
Linkvulncheck.com · advisories/erpnext-15.94.2-before-15.122.0-unauthorized-supplier-portal-record-access-via-party-name-collision

Questions about CVE-2026-134406

Is CVE-2026-134406 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 read buying-portal records outside their permitted scope by passing a party identity check with a colliding name. The flaw is that ERPNext fails to distinguish a Customer and a Supplier that share the same name.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134406?

erpnext: from 15.94.2 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?

ERPNext 15.94.2 before 15.122.0 and 16.x before 16.50.0 are affected, and only where a Customer and a Supplier share the same name. To check, look at the installed ERPNext version and search the Customer and Supplier lists for matching names.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134406?

Upgrade ERPNext to 15.122.0 or 16.50.0, the fixed versions for each affected branch.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.