CVE-2026-24002

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

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

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

The CVE record names the fixed release — apply it.

Grist is spreadsheet software using Python as its formula language. Grist offers several methods for running those formulas in a sandbox, for cases where the user may be working with untrusted spreadsheets. One such method runs them in pyodide, but pyodide on node does not have a useful sandbox barrier. If a user of Grist sets GRIST_SANDBOX_FLAVOR to pyodide and opens a malicious document, that document could run arbitrary processes on the server hosting Grist. The problem has been addressed in Grist version 1.7.9 and up, by running pyodide under deno. As a workaround, a user can use the gvisor-based sandbox by setting GRIST_SANDBOX_FLAVOR to gvisor.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/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)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
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 (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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).

The CVE record names the fixed release. 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

January 22, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Fix named in the CVE record. Sources: github.
Web page

Self-hosted Grist - Grist Help Center

https://support.getgrist.com/self-managed/#how-do-i-sandbox-documents
GitHub advisoryMentions a patch (unverified)

pyodide sandbox option is insecure · Advisory · gristlabs/grist-core · GitHub

https://github.com/gristlabs/grist-core/security/advisories/GHSA-7xvx-8pf2-pv5g

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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 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). "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 245 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 145 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24002?
CVE-2026-24002 is a critical-severity vulnerability; its CVE record was published on January 22, 2026. Grist is spreadsheet software using Python as its formula language. Grist offers several methods for running those formulas in a sandbox, for cases where the user may be working with untrusted spreadsheets. One such method runs them in pyodide, but pyodide on node does not have a useful sandbox…
When was the CVE record for CVE-2026-24002 published?
The CVE record for CVE-2026-24002 was published on January 22, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-24002 actively exploited?
CVE-2026-24002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24002?
CVE-2026-24002 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-24002?
The CVE record for CVE-2026-24002 names the fix: "The problem has been addressed in Grist version 1.7.9 and up, by running pyodide under deno."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-24002?

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

Book a Demo →Browse All CVEs