CVE-2026-62315

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Frappe is a full-stack web application framework. In version 16.31.0 and earlier, frappe.client.set_value in frappe/client.py checks a dictionary supplied through the fieldname parameter against forbidden standard and child-table fields before parsing the dictionary into individual field names. An authenticated caller can exploit this type confusion to mass-assign protected fields through the client endpoint. No released fixed version is available as of this review.

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

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 20, 2026

Last Modified

September 10, 2026

Advisory Details (3)

Auto-updated Aug 20, 2026
No fix on record yet. Sources: github, github_pr, github_commit.
github_commit

commit 2a04fae9353c (frappe/frappe)

Fix landed in frappe/frappe commit 2a04fae9353c — awaiting tagged release

https://github.com/frappe/frappe/commit/2a04fae9353c02f0a9ce9f40f92c1eba6765c77b
github_pr

fix(client): add proper checks to client.py endpoints.

Fix merged in frappe/frappe PR #38951 on 2026-06-26 — awaiting tagged release

https://github.com/frappe/frappe/pull/38951
githubMentions a patch (unverified)

Mass assignment in client endpoint · Advisory · frappe/frappe · GitHub

https://github.com/frappe/frappe/security/advisories/GHSA-2c6h-wv85-fxvj

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 47× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62315?
CVE-2026-62315 is a high vulnerability published on August 20, 2026. Frappe is a full-stack web application framework. In version 16.31.0 and earlier, frappe.client.set_value in frappe/client.py checks a dictionary supplied through the fieldname parameter against forbidden standard and child-table fields before parsing the dictionary into individual field names. An…
When was CVE-2026-62315 disclosed?
CVE-2026-62315 was first published on August 20, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62315 actively exploited?
CVE-2026-62315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62315?
CVE-2026-62315 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-62315?
No fix for CVE-2026-62315 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62315?

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

Book a Demo →Browse All CVEs