{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24002 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24002 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-24002 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-24002 in the wild and no public exploit code.\n\nAffected product: gristlabs grist-core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24002/ (Markdown: https://insights.sbomify.com/CVE-2026-24002/index.md)","id":"CVE-2026-24002","markdown":"https://insights.sbomify.com/CVE-2026-24002/index.md","name":"CVE-2026-24002","record":{"aliases":["GHSA-7xvx-8pf2-pv5g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Grist spreadsheet software","requires_auth":"none","summary":"Attackers can execute arbitrary code on the server if Grist is configured to use the insecure pyodide sandbox flavor.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"grist-core","vendor":"getgrist"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"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`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"pyodide sandbox option is insecure","id":"CVE-2026-24002","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"EvseV2G has sequence state validation bypass","id":"CVE-2026-24003"},"packages":[],"prev":{"headline":"jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch","id":"CVE-2026-24001"},"products":["grist-core"],"published":"2026-01-22","related":[{"cvss_score":8.1,"headline":"Cross-site Scripting vulnerability through custom widget URLs and form redirect URLs in grist-core","id":"CVE-2024-56357","kev_date_added":null,"published":"2024-12-20"},{"cvss_score":8.1,"headline":"Cross-site Scripting vulnerability through svg attachment previews in grist-core","id":"CVE-2024-56358","kev_date_added":null,"published":"2024-12-20"},{"cvss_score":8.1,"headline":"Cross-site Scripting vulnerability through HyperLink cells in grist-core","id":"CVE-2024-56359","kev_date_added":null,"published":"2024-12-20"},{"cvss_score":6.8,"headline":"grist-core has path to server-side requests via websocket","id":"CVE-2025-64752","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":5.3,"headline":"grist-core has insufficient access control in endpoints for comparisons between documents and versions","id":"CVE-2025-64753","kev_date_added":null,"published":"2025-11-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["gristlabs"]},"summary":"Attackers can execute arbitrary code on the server if Grist is configured to use the insecure pyodide sandbox flavor.","url":"https://insights.sbomify.com/CVE-2026-24002/"}