CVE-2026-67618
marimo before 0.23.15 contains a configuration injection …
marimo before 0.23.15 contains a configuration injection vulnerability that allows notebook authors to exfiltrate operator API keys by embedding a malicious base_url in PEP-723 inline script metadata, which is merged into session configuration with higher precedence than the operator's own settings due to insufficient sanitization in sanitize_pyproject_dict. When an operator opens the crafted notebook and makes an AI request, marimo resolves the attacker-controlled base_url from the notebook config while falling back to the operator's OPENAI_API_KEY environment variable for authentication, transmitting the API key to the attacker-controlled endpoint without requiring any cell execution.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/marimo-team/marimo/commit/1a21bd71e258438d2511136b5edacc94c08855f4
- github.com/marimo-team/marimo/pull/10281
- github.com/marimo-team/marimo/releases/tag/0.23.15
- www.vulncheck.com/advisories/marimo-api-key-exfiltration-via-malicious-notebook-pep-723-me
- nvd.nist.gov/vuln/detail/CVE-2026-67618
- cve.org/CVERecord?id=CVE-2026-67618
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.