Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 17 Feb 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Getgrist
Getgrist grist-core |
|
| CPEs | cpe:2.3:a:getgrist:grist-core:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Getgrist
Getgrist grist-core |
Fri, 23 Jan 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gristlabs
Gristlabs grist-core |
|
| Vendors & Products |
Gristlabs
Gristlabs grist-core |
Thu, 22 Jan 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 22 Jan 2026 02:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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`. | |
| Title | pyodide sandbox option is insecure | |
| Weaknesses | CWE-74 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-22T12:54:32.232Z
Reserved: 2026-01-19T18:49:20.658Z
Link: CVE-2026-24002
Updated: 2026-01-22T12:54:25.326Z
Status : Analyzed
Published: 2026-01-22T03:15:47.777
Modified: 2026-02-17T17:59:16.383
Link: CVE-2026-24002
No data.
OpenCVE Enrichment
Updated: 2026-04-18T04:00:08Z