CVE-2026-67618: Insufficient Verification of Data Authenticity in marimo-team marimo
marimo versions prior to 0.23.15 contain a configuration injection vulnerability that allows malicious notebook authors to exfiltrate operator API keys. This occurs because attacker-controlled base_url values embedded in notebook metadata override operator settings without proper sanitization. When an operator opens a crafted notebook and makes an AI request, the operator's API key is sent to the attacker-controlled endpoint without requiring execution of notebook cells.
AI Analysis
Technical Summary
CVE-2026-67618 describes a configuration injection vulnerability in marimo before version 0.23.15. The vulnerability arises from insufficient sanitization in the sanitize_pyproject_dict function, allowing an attacker to embed a malicious base_url in PEP-723 inline script metadata within a notebook. This attacker-controlled base_url is merged into the session configuration with higher precedence than the operator's own settings. When an operator opens the malicious notebook and initiates an AI request, marimo uses the attacker-controlled base_url while authenticating with the operator's OPENAI_API_KEY environment variable, resulting in the API key being transmitted to the attacker-controlled endpoint without any need for executing notebook cells.
Potential Impact
An attacker who crafts a malicious notebook can exfiltrate the operator's API key by embedding a malicious base_url in the notebook metadata. This compromises the confidentiality of the operator's API key, potentially allowing unauthorized access to AI services or other resources tied to that key. The vulnerability does not require the operator to execute any notebook cells, increasing the risk of unnoticed key leakage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, operators should avoid opening notebooks from untrusted sources. Monitoring for suspicious network activity related to API key usage is recommended. Follow vendor communications for updates on official patches or mitigations.
CVE-2026-67618: Insufficient Verification of Data Authenticity in marimo-team marimo
Description
marimo versions prior to 0.23.15 contain a configuration injection vulnerability that allows malicious notebook authors to exfiltrate operator API keys. This occurs because attacker-controlled base_url values embedded in notebook metadata override operator settings without proper sanitization. When an operator opens a crafted notebook and makes an AI request, the operator's API key is sent to the attacker-controlled endpoint without requiring execution of notebook cells.
CVSS v4.0
Score 7.1high
Affected software
marimo-team
marimo
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-67618 describes a configuration injection vulnerability in marimo before version 0.23.15. The vulnerability arises from insufficient sanitization in the sanitize_pyproject_dict function, allowing an attacker to embed a malicious base_url in PEP-723 inline script metadata within a notebook. This attacker-controlled base_url is merged into the session configuration with higher precedence than the operator's own settings. When an operator opens the malicious notebook and initiates an AI request, marimo uses the attacker-controlled base_url while authenticating with the operator's OPENAI_API_KEY environment variable, resulting in the API key being transmitted to the attacker-controlled endpoint without any need for executing notebook cells.
Potential Impact
An attacker who crafts a malicious notebook can exfiltrate the operator's API key by embedding a malicious base_url in the notebook metadata. This compromises the confidentiality of the operator's API key, potentially allowing unauthorized access to AI services or other resources tied to that key. The vulnerability does not require the operator to execute any notebook cells, increasing the risk of unnoticed key leakage.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, operators should avoid opening notebooks from untrusted sources. Monitoring for suspicious network activity related to API key usage is recommended. Follow vendor communications for updates on official patches or mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-29T21:07:39.203Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a71fdb7bf8831d539fada0a
Added to database: 08/04/2026, 14:56:55 UTC
Last enriched: 08/11/2026, 18:30:01 UTC
Last updated: 09/18/2026, 10:01:33 UTC
Views: 50
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.