CVE-2026-66001

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th 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

Also known asEUVD-2026-63540 (ENISA EUVD)Source: ENISA EUVD

8.5EG
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.3%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Frappe is a full-stack web application framework. Prior to 15.114.0 and 16.26.0, the approve and authorize functions in frappe/integrations/oauth2.py allow the OAuth2 consent flow to proceed without restricting approve to POST, without a csrf_token in frappe/templates/includes/oauth_confirmation.html, and without scoping an active OAuth token check to the requesting client. An attacker can cause an authenticated user to approve an OAuth grant or reuse authorization state for the wrong client, exposing data and permitting actions within the granted scopes. This issue is fixed in versions 15.114.0 and 16.26.0.

CVSS
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 20, 2026

Last Modified

October 26, 2026

Advisory Details (9)

Auto-updated Aug 20, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

v16.26.0

Patch available: frappe/frappe v16.26.0

https://github.com/frappe/frappe/releases/tag/v16.26.0
GitHub release Patch Available

v15.114.0

Patch available: frappe/frappe v15.114.0

https://github.com/frappe/frappe/releases/tag/v15.114.0
GitHub commit Patch Available

commit eb9c1446cac1 (frappe/frappe)

Patch available: frappe/frappe v16.26.0 (contains commit eb9c1446cac1)

https://github.com/frappe/frappe/commit/eb9c1446cac13236c6d573b136786db2e46254fa
GitHub commit Patch Available

commit d7460769f999 (frappe/frappe)

Patch available: frappe/frappe v15.114.0 (contains commit d7460769f999)

https://github.com/frappe/frappe/commit/d7460769f999c68d3121b680119f8724ddd3eb9d
GitHub commit

commit 336c7d335db7 (frappe/frappe)

Fix landed in frappe/frappe commit 336c7d335db7 — awaiting tagged release

https://github.com/frappe/frappe/commit/336c7d335db762b494acdfe43aea69d459fd51d7
GitHub pull request Patch Available

fix: hardening oauth endpoints (backport #40073)

Patch available: frappe/frappe v15.114.0 (PR #40701 merged 2026-07-09)

https://github.com/frappe/frappe/pull/40701
GitHub pull request Patch Available

fix: hardening oauth endpoints (backport #40073)

Patch available: frappe/frappe v16.26.0 (PR #40700 merged 2026-07-09)

https://github.com/frappe/frappe/pull/40700
GitHub pull request

fix: hardening oauth endpoints

Fix merged in frappe/frappe PR #40073 on 2026-07-09 — awaiting tagged release

https://github.com/frappe/frappe/pull/40073
GitHub advisoryMentions a patch (unverified)

Improper Authorization in OAuth2 Consent Endpoint · Advisory · frappe/frappe · GitHub

https://github.com/frappe/frappe/security/advisories/GHSA-2ph8-x773-8p2x

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 132 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-11-10 08:31 UTCEchelonGraph re-scored
  6. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-11-03 15:35 UTCEchelonGraph re-scored
  14. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  15. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  18. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  19. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  20. 2026-10-27 21:06 UTCEchelonGraph re-scored
  21. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  22. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  23. 2026-10-26 10:26 UTCEchelonGraph re-scored
  24. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  25. 2026-10-25 14:11 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-20 09:08 UTCEchelonGraph re-scored
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-18 03:21 UTCEchelonGraph re-scored
  10. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-13 11:02 UTCEchelonGraph re-scored
  16. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-12 15:46 UTCEchelonGraph re-scored
  18. 2026-10-11 19:31 UTCEchelonGraph re-scored
  19. 2026-10-11 16:46 UTCEchelonGraph re-scored
  20. 2026-10-11 14:07 UTCEchelonGraph re-scored
  21. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-09 08:23 UTCEchelonGraph re-scored
  25. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  26. 2026-10-08 05:18 UTCEchelonGraph re-scored
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  28. 2026-10-06 16:53 UTCEchelonGraph re-scored
  29. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-10-06 03:20 UTCEchelonGraph re-scored
  31. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  32. 2026-10-05 09:29 UTCEchelonGraph re-scored
  33. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-10-03 16:47 UTCEchelonGraph re-scored
  35. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  36. 2026-10-03 01:36 UTCEchelonGraph re-scored
  37. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  38. 2026-10-01 22:44 UTCEchelonGraph re-scored
  39. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  40. 2026-09-30 20:47 UTCEchelonGraph re-scored
  41. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  42. 2026-09-30 08:12 UTCEchelonGraph re-scored
  43. 2026-09-28 21:38 UTCEchelonGraph re-scored
  44. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  45. 2026-09-27 15:56 UTCEchelonGraph re-scored
  46. 2026-09-27 02:59 UTCEchelonGraph re-scored
  47. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  48. 2026-09-25 02:12 UTCEchelonGraph re-scored
  49. 2026-09-24 01:03 UTCEchelonGraph re-scored
  50. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-09-22 23:54 UTCEchelonGraph re-scored
  52. 2026-09-21 22:44 UTCEchelonGraph re-scored
  53. 2026-09-20 21:35 UTCEchelonGraph re-scored
  54. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-09-19 18:28 UTCEchelonGraph re-scored
  56. 2026-09-19 05:50 UTCEchelonGraph re-scored
  57. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  58. 2026-09-18 04:38 UTCEchelonGraph re-scored
  59. 2026-09-17 03:28 UTCEchelonGraph re-scored
  60. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  61. 2026-09-16 11:00 UTCEchelonGraph re-scored
  62. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  63. 2026-09-15 09:51 UTCEchelonGraph re-scored
  64. 2026-09-13 19:57 UTCEchelonGraph re-scored
  65. 2026-09-12 18:46 UTCEchelonGraph re-scored
  66. 2026-09-11 17:33 UTCEchelonGraph re-scored
  67. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  69. 2026-09-10 15:42 UTCEchelonGraph re-scored
  70. 2026-09-09 01:55 UTCEchelonGraph re-scored
  71. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  72. 2026-09-08 04:07 UTCEchelonGraph re-scored
  73. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  74. 2026-09-07 02:43 UTCEchelonGraph re-scored
  75. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile

Frequently asked(5)

What is CVE-2026-66001?
CVE-2026-66001 is a high-severity vulnerability; its CVE record was published on August 20, 2026. Frappe is a full-stack web application framework. Prior to 15.114.0 and 16.26.0, the approve and authorize functions in frappe/integrations/oauth2.py allow the OAuth2 consent flow to proceed without restricting approve to POST, without a csrf_token in…
When was the CVE record for CVE-2026-66001 published?
The CVE record for CVE-2026-66001 was published on August 20, 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 October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-66001 actively exploited?
CVE-2026-66001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66001?
CVE-2026-66001 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66001?
A fix for CVE-2026-66001 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-66001

Explore →

Is Your Infrastructure Affected by CVE-2026-66001?

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