VulnerabilityPublished 4 Aug 2026

CVE-2026-67618: marimo · Insufficient Verification of Data Authenticity

Affects marimoSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 0.23.15 soon.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 4.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.23.15

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-v9v8-jp27-55gf

What to do

Upgrade marimo to 0.23.15.

Affected software

Product	Affected	Fixed in
marimo-teammarimo	Affected <0.23.15	Fixed in–
GitHubmarimo`pkg:github/marimo`Other threats	Affected <0.23.15	Fixed in 0.23.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, 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.

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.

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.

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.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Aug 2026, 18:30 UTC

Technical details

References

Community reviews

Related threats