CVE-2026-66003

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 26, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Access control bypass via REST API · Advisory · frappe/frappe · GitHub

https://github.com/frappe/frappe/security/advisories/GHSA-p25m-7rvg-6fvr
GitHub release Patch Available

v15.115.0

Patch available: frappe/frappe v15.115.0

https://github.com/frappe/frappe/releases/tag/v15.115.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-13 11:02 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-12 15:46 UTCEG score recompute
  5. 2026-10-11 19:31 UTCEG score recompute
  6. 2026-10-11 16:46 UTCEG score recompute
  7. 2026-10-11 14:07 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-10 06:04 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-10-09 03:20 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-08 01:46 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-06 21:22 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-05 20:29 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-05 08:05 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-03 16:05 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-10-02 21:44 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 60 more
  1. 2026-10-01 20:57 UTCEG score recompute
  2. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-09-30 19:58 UTCEG score recompute
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-09-30 06:01 UTCEG score recompute
  6. 2026-09-28 22:22 UTCEG score recompute
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-09-27 21:19 UTCEG score recompute
  9. 2026-09-26 20:32 UTCEG score recompute
  10. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-09-24 22:10 UTCEG score recompute
  12. 2026-09-23 20:37 UTCEG score recompute
  13. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-09-22 19:50 UTCEG score recompute
  15. 2026-09-22 07:27 UTCEG score recompute
  16. 2026-09-21 06:38 UTCEG score recompute
  17. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-09-19 17:27 UTCEG score recompute
  19. 2026-09-19 05:03 UTCEG score recompute
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-09-18 04:14 UTCEG score recompute
  22. 2026-09-16 15:03 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-09-15 14:13 UTCEG score recompute
  26. 2026-09-14 01:01 UTCEG score recompute
  27. 2026-09-13 00:10 UTCEG score recompute
  28. 2026-09-11 23:21 UTCEG score recompute
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-11 10:54 UTCEG score recompute
  31. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  32. 2026-09-10 09:37 UTCEG score recompute
  33. 2026-09-09 00:48 UTCEG score recompute
  34. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  35. 2026-09-08 03:33 UTCEG score recompute
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  37. 2026-09-07 02:13 UTCEG score recompute
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-06 01:24 UTCEG score recompute
  40. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  41. 2026-09-05 00:37 UTCEG score recompute
  42. 2026-09-04 12:12 UTCEG score recompute
  43. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-09-02 22:33 UTCEG score recompute
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-09-01 21:45 UTCEG score recompute
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-09-01 09:21 UTCEG score recompute
  49. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-08-30 20:01 UTCEG score recompute
  51. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-08-30 07:37 UTCEG score recompute
  53. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  54. 2026-08-29 06:46 UTCEG score recompute
  55. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  56. 2026-08-27 17:31 UTCEG score recompute
  57. 2026-08-27 17:07 UTCEG score recompute
  58. 2026-08-26 20:26 UTCEG score recompute
  59. 2026-08-26 20:07 UTCEG score recomputeFirst assessed: 7.1 HIGH
  60. 2026-08-26 20:06 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-66003?
CVE-2026-66003 is a high-severity vulnerability; its CVE record was published on August 26, 2026. 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…
When was the CVE record for CVE-2026-66003 published?
The CVE record for CVE-2026-66003 was published on August 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-66003 actively exploited?
CVE-2026-66003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66003?
CVE-2026-66003 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66003?
A fix for CVE-2026-66003 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-66003

Explore →

Is Your Infrastructure Affected by CVE-2026-66003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs