Frappe is a full-stack web application framework written in Python and JavaScript. Prior to version 15.115.0, an access control bypass in the REST API allows a user to read data from Linked DocTypes that they are not authorized to access. When a document references another document through a Link field, the framework does not consistently enforce the linked DocType's own permissions when the record is retrieved through the REST API, so a low-privileged authenticated user can obtain fields from linked records outside their permitted scope. This issue is fixed in version 15.115.0.
CVE-2026-66003
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 27, 2026
Advisory Details (2)
Auto-updated Aug 26, 2026Access control bypass via REST API · Advisory · frappe/frappe · GitHub
https://github.com/frappe/frappe/security/advisories/GHSA-p25m-7rvg-6fvrv15.115.0
Patch available: frappe/frappe v15.115.0
https://github.com/frappe/frappe/releases/tag/v15.115.0Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 06:46 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 17:31 UTCEG score recompute
- 2026-08-27 17:07 UTCEG score recompute
- 2026-08-26 20:26 UTCEG score recompute
- 2026-08-26 20:07 UTCEG score recompute
- 2026-08-26 20:06 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-66003?
When was CVE-2026-66003 disclosed?
Is CVE-2026-66003 actively exploited?
What is the CVSS score of CVE-2026-66003?
How do I remediate CVE-2026-66003?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66003
Is Your Infrastructure Affected by CVE-2026-66003?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.