{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-67618 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-67618 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-67618 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-67618 in the wild and no public exploit code.\n\nAffected product: marimo-team marimo. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67618/ (Markdown: https://insights.sbomify.com/CVE-2026-67618/index.md)","id":"CVE-2026-67618","markdown":"https://insights.sbomify.com/CVE-2026-67618/index.md","name":"CVE-2026-67618","record":{"aliases":["GHSA-v9v8-jp27-55gf"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python notebook tool","requires_auth":"none","summary":"Attackers can exfiltrate operator API keys by embedding malicious metadata in notebooks, causing keys to be sent to attacker-controlled endpoints.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"marimo \u003c 0.23.15 API Key Exfiltration via Malicious Notebook PEP-723 Metadata","id":"CVE-2026-67618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2026-67619"},"packages":[],"prev":{"headline":"Microweber CMS 2.0.20 Stored XSS via tag_names Parameter","id":"CVE-2026-67617"},"products":["marimo"],"published":"2026-08-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-04","vendors":["marimo-team"]},"summary":"Attackers can exfiltrate operator API keys by embedding malicious metadata in notebooks, causing keys to be sent to attacker-controlled endpoints.","url":"https://insights.sbomify.com/CVE-2026-67618/"}