Skip to main content
Menu
CVEs

Frappe ERPNext unauthorized BOM replacement in manufacturing

Affects Frappe ERPNext 10.1.41 up to 15.122.0, and 16.x before 16.50.0, where an authenticated user can replace BOMs across the whole site. Fixed in 15.122.0 and 16.50.0.

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

8.3HighCNA
Exploited
No known exploitation
Fix
Fixed in 15.122.0, 16.50.0
Who is exposed
Specific setups only

Summary

Frappe ERPNext has a missing authorization flaw in its Manufacturing module that lets a logged-in user who can create a BOM Update Log send a crafted request over the network to replace one bill of materials with another across every assembly on the site. The vendor and product come from the affected data, so the title names Frappe ERPNext.

Written by a model

Original description

Frappe ERPNext 10.1.41 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in a Manufacturing module endpoint that replaces BOMs without checking whether the caller may modify either BOM or the affected assemblies. Authenticated users who can create a BOM Update Log can send a crafted request naming two BOMs to replace the first with the second in every assembly site-wide.

Who should check

Teams running Frappe ERPNext 10.x through 15.x before 15.122.0, or 16.x before 16.50.0, where users can create BOM Update Logs.

“Frappe ERPNext 10.1.41 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.

    Frappe ERPNext 10.1.41 up to before 15.122.0, or 16.x before 16.50.0
  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-134393 (Frappe ERPNext 10.1.41 before 15.122.0 Missing Authorization in Manufacturing BOM Replacement), 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-134393 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 10.1.41, 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 10.1.41 up to before 15.122.0, or 16.x before 16.50.0 (source: https://www.vulncheck.com/advisories/frappe-erpnext-10.1.41-before-15.122.0-missing-authorization-in-manufacturing-bom-replacement)
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-134393 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134393 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-77q9-p3mx-p357
- https://www.vulncheck.com/advisories/frappe-erpnext-10.1.41-before-15.122.0-missing-authorization-in-manufacturing-bom-replacement
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-134393
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-134393"}.

Affected versions

cve.now Index

16Pof 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
  • Severity8.3/10CVSS 8.3
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 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-77q9-p3mx-p357
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134393
RecordNVD · CVE-2026-134393
Other links 1
Linkvulncheck.com · advisories/frappe-erpnext-10.1.41-before-15.122.0-missing-authorization-in-manufacturing-bom-replacement

Questions about CVE-2026-134393

Is CVE-2026-134393 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?

Because of missing authorization checks in the Manufacturing BOM Replacement feature, an authenticated user can replace bills of materials (BOMs) across the whole site, including outside their permitted scope.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134393?

erpnext: from 10.1.41 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 10.1.41 before 15.122.0, and 16.x before 16.50.0. Compare the installed ERPNext version against these ranges to see which range it falls in.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134393?

Upgrade ERPNext to 15.122.0 or later in the 15.x line, or to 16.50.0 or later in the 16.x line.

Source: vulncheck.com, github.com

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