CVE-2026-67618: marimo < 0.23.15 API Key Exfiltration via Malicious Notebook PEP-723 Metadata
marimo before 0.23.15 contains a configuration injection vulnerability that allows notebook authors to exfiltrate operator API keys by embedding a malicious baseurl 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 sanitizepyprojectdict. When an operator opens the crafted notebook and makes an AI request, marimo resolves the attacker-controlled baseurl from the notebook config while falling back to the operator's OPENAIAPIKEY environment variable for authentication, transmitting the API key to the attacker-controlled endpoint without requiring any cell execution.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
marimoto a version that resolves this vulnerability.Fixed in 0.23.15 - Operational
Rotate any OpenAI API keys that may have been exposed to an attacker-controlled base_url when opening a malicious marimo notebook.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67618?
The severity of CVE-2026-67618 is medium with a score of 6.5.
What is CVE-2026-67618 about?
CVE-2026-67618 describes a configuration injection vulnerability in marimo that can lead to API key exfiltration.
How do I fix CVE-2026-67618?
To mitigate CVE-2026-67618, upgrade marimo to version 0.23.15 or later.
What can be exploited in CVE-2026-67618?
CVE-2026-67618 can be exploited by embedding a malicious base_url in PEP-723 inline script metadata.
What impact does CVE-2026-67618 have?
The impact of CVE-2026-67618 can lead to exposure of sensitive operator API keys.