# CVE-2026-24002: pyodide sandbox option is insecure

> Attackers can execute arbitrary code on the server if Grist is configured to use the insecure pyodide sandbox flavor.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-7xvx-8pf2-pv5g

## What is CVE-2026-24002?

CVE-2026-24002 is a critical code injection vulnerability in gristlabs grist-core, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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`.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-24002?

It affects 1 product.


Products: Getgrist Grist-Core.

## How do I fix CVE-2026-24002?

No fix has been published for CVE-2026-24002 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24002 being exploited?

There is no known exploitation of CVE-2026-24002 in the wild and no public exploit code.

## Other vulnerabilities in gristlabs grist-core

- [CVE-2024-56357](https://insights.sbomify.com/CVE-2024-56357/): Cross-site Scripting vulnerability through custom widget URLs and form redirect URLs in grist-core (high 8.1)
- [CVE-2024-56358](https://insights.sbomify.com/CVE-2024-56358/): Cross-site Scripting vulnerability through svg attachment previews in grist-core (high 8.1)
- [CVE-2024-56359](https://insights.sbomify.com/CVE-2024-56359/): Cross-site Scripting vulnerability through HyperLink cells in grist-core (high 8.1)
- [CVE-2025-64752](https://insights.sbomify.com/CVE-2025-64752/): grist-core has path to server-side requests via websocket (medium 6.8)
- [CVE-2025-64753](https://insights.sbomify.com/CVE-2025-64753/): grist-core has insufficient access control in endpoints for comparisons between documents and versions (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24002 and fix it if it is affected.

What it is: CVE-2026-24002 is a critical code injection vulnerability in gristlabs grist-core, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24002 in the wild and no public exploit code.

Affected product: gristlabs grist-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24002/ (Markdown: https://insights.sbomify.com/CVE-2026-24002/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24002
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24002
- OSV: https://osv.dev/vulnerability/CVE-2026-24002

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24002/
Summaries are generated and may contain mistakes; the official description above is the record.