CVE-2026-67618 marimo < 0.23.15 API Key Exfiltration via Malicious Notebook PEP-723 Metadata
Attackers can exfiltrate operator API keys by embedding malicious metadata in notebooks, causing keys to be sent to attacker-controlled endpoints.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-67618?
CVE-2026-67618 is a high-severity vulnerability in marimo-team marimo, published on 4 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-345
Which versions are affected by CVE-2026-67618?
How do I fix CVE-2026-67618?
No fix has been published for CVE-2026-67618 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-67618 being exploited?
There is no known exploitation of CVE-2026-67618 in the wild and no public exploit code.
Sources
Also known as GHSA-v9v8-jp27-55gf.