marimo < 0.23.15 API Key Exfiltration via Malicious Notebook PEP-723 Metadata
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| marimo-team | marimo | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Marimo-team | Marimo |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.295% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Marimo-team
Marimo-team marimo |
|
| Vendors & Products |
Marimo-team
Marimo-team marimo |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | marimo < 0.23.15 API Key Exfiltration via Malicious Notebook PEP-723 Metadata | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV3_1
|