Skip to main content
Menu
CVEs

Frappe ERPNext unauthorized address access via tax rule endpoint

ERPNext 6.3.0 up to 15.122.0 and 16.x before 16.50.0 are affected. Fixed in 15.122.0 and 16.50.0. CVSS scores this 5.3 (medium); no vendor severity is given.

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

5.3MediumCNA
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 check in its Accounts module endpoint used to pick a Tax Rule, which returns party address details without permission checks. A remote attacker who has a low-privilege login, including portal users or users with no roles, can request the city, state, postal code, and country for arbitrary customers, suppliers, or addresses.

Written by a model

Original description

Frappe ERPNext 6.3.0 before 15.122.0 and 16.x before 16.50.0 contains a missing authorization vulnerability in an Accounts module endpoint used to choose a Tax Rule, which returns party address details without permission checks. Authenticated attackers, including portal users or users with no roles, can send crafted requests naming arbitrary customers, suppliers, or Addresses to obtain their city, state, postal code, and country.

Who should check

Teams running Frappe ERPNext 6.3.0 up to before 15.122.0, or 16.x before 16.50.0, where authenticated users such as portal users can log in

“Affecting erpnext >= 6.3.0, < 15.122.0”

vulncheck.com

What to do

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

    ERPNext 6.3.0 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-134385 (Frappe ERPNext 6.3.0 before 15.122.0 Unauthorized Address Access via Tax Rule 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-134385 (entry last updated 2026-11-21):
Affected:
- frappe erpnext: from 6.3.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):
- ERPNext 6.3.0 up to before 15.122.0, or 16.x before 16.50.0 (source: https://www.vulncheck.com/advisories/frappe-erpnext-6.3.0-before-15.122.0-unauthorized-address-access-via-tax-rule-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-134385 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134385 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-8mhv-pfp8-m66q
- https://www.vulncheck.com/advisories/frappe-erpnext-6.3.0-before-15.122.0-unauthorized-address-access-via-tax-rule-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-134385
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-134385"}.

Affected versions

cve.now Index

13Pof 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
  • 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

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

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · frappe/erpnext · Advisory GHSA-8mhv-pfp8-m66q
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134385
RecordNVD · CVE-2026-134385
Other links 1
Linkvulncheck.com · advisories/frappe-erpnext-6.3.0-before-15.122.0-unauthorized-address-access-via-tax-rule-endpoint

Questions about CVE-2026-134385

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

The Tax Rule endpoint returned the city, state, postal code and country of arbitrary Addresses, including customer and supplier addresses, to an authenticated user who should not see them.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134385?

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

ERPNext from 6.3.0 before 15.122.0, and 16.x before 16.50.0. To check a deployment, compare its installed ERPNext version against these ranges.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134385?

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

Source: vulncheck.com, github.com

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