Skip to main content
Menu
CVEs

Frappe ERPNext missing authorization exposes CRM and Support emails

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

8.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 15.121.4, 16.36.0
Who is exposed
Specific setups only

Summary

Frappe ERPNext before 15.121.4 and 16.x before 16.36.0 contains a missing authorization vulnerability in a CRM and Support module endpoint that returns Communications of documents without checking whether the caller may read them. Authenticated attackers with a common operational role can send crafted requests naming out-of-scope records to read their email communications and relink them away from their original documents.

Who should check

Teams running Frappe ERPNext before 15.121.4 or 16.x before 16.36.0, including those using the CRM and Support modules

“Frappe ERPNext before 15.121.4 and 16.x before 16.36.0”

vulncheck.com

What to do

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

    Frappe ERPNext before 15.121.4, or 16.x before 16.36.0 The affected endpoint in the CRM and Support modules
  2. Upgrade to a fixed version: 15.121.4, 16.36.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-134429 (Frappe ERPNext before 15.121.4 Missing Authorization in CRM and Support Communications), 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-134429 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: 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):
- Frappe ERPNext before 15.121.4, or 16.x before 16.36.0 (source: https://www.vulncheck.com/advisories/frappe-erpnext-before-15.121.4-missing-authorization-in-crm-and-support-communications)
- The affected endpoint in the CRM and Support modules (source: https://www.vulncheck.com/advisories/frappe-erpnext-before-15.121.4-missing-authorization-in-crm-and-support-communications)
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-134429 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134429 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-5q53-5vm3-cjq8
- https://www.vulncheck.com/advisories/frappe-erpnext-before-15.121.4-missing-authorization-in-crm-and-support-communications
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-134429
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-134429"}.

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.4/10CVSS 8.4
  • 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-5q53-5vm3-cjq8
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134429
RecordNVD · CVE-2026-134429
Other links 1
Linkvulncheck.com · advisories/frappe-erpnext-before-15.121.4-missing-authorization-in-crm-and-support-communications

Questions about CVE-2026-134429

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

Authenticated users can read email communications on documents they are not permitted to read. They can also relink those communications away from their original documents.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134429?

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

Source: cve.now feed data

Am I affected, and how do I check?

ERPNext versions before 15.121.4 and 16.x versions before 16.36.0 are affected, through an endpoint in the CRM and Support modules. To check a version, look at the ERPNext version shown in the app's about or version information for the installed bench.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134429?

Upgrade to ERPNext 15.121.4 or later on the 15.x line, or to 16.36.0 or later on the 16.x line. The facts do not name a separate workaround.

Source: vulncheck.com, github.com

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