CVE-2026-67618

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 4, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
Patch available. Sources: github_commit, github_release, github_pr.
generic

marimo < 0.23.15 API Key Exfiltration via Malicious Notebook PEP-723 Metadata | Advisories | VulnCheck

https://www.vulncheck.com/advisories/marimo-api-key-exfiltration-via-malicious-notebook-pep-723-metadata
github_commit Patch Available

commit 1a21bd71e258 (marimo-team/marimo)

Patch available: marimo-team/marimo 0.23.15 (contains commit 1a21bd71e258)

https://github.com/marimo-team/marimo/commit/1a21bd71e258438d2511136b5edacc94c08855f4
github_pr Patch Available

fix: additional pep 723 sanitization

Patch available: marimo-team/marimo 0.23.15 (PR #10281 merged 2026-07-23)

https://github.com/marimo-team/marimo/pull/10281
github_release Patch Available

0.23.15

Patch available: marimo-team/marimo 0.23.15

https://github.com/marimo-team/marimo/releases/tag/0.23.15

Vendor Advisories for CVE-2026-67618(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 09:07 UTCEG score recompute
  3. 2026-08-20 09:07 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 10:58 UTCEG score recompute
  6. 2026-08-19 10:58 UTCGHSA enrichment
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-18 12:49 UTCGHSA enrichment
  9. 2026-08-17 14:33 UTCEG score recompute
  10. 2026-08-17 14:33 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 16:24 UTCEG score recompute
  13. 2026-08-16 16:24 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-15 18:16 UTCEG score recompute
  16. 2026-08-15 18:16 UTCGHSA enrichment
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 20:07 UTCEG score recompute
  19. 2026-08-14 20:07 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 21:58 UTCGHSA enrichment
  22. 2026-08-12 23:49 UTCEG score recompute
  23. 2026-08-12 23:49 UTCGHSA enrichment
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-12 01:41 UTCEG score recompute
Show 25 more
  1. 2026-08-12 01:41 UTCGHSA enrichment
  2. 2026-08-11 03:32 UTCEG score recompute
  3. 2026-08-11 03:32 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 05:23 UTCEG score recompute
  6. 2026-08-10 05:23 UTCGHSA enrichment
  7. 2026-08-09 13:47 UTCEPSS rescore
  8. 2026-08-09 07:15 UTCEG score recompute
  9. 2026-08-09 07:15 UTCGHSA enrichment
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-08 09:07 UTCEG score recompute
  12. 2026-08-08 09:07 UTCGHSA enrichment
  13. 2026-08-07 10:58 UTCEG score recompute
  14. 2026-08-07 10:58 UTCGHSA enrichment
  15. 2026-08-06 13:47 UTCEPSS rescore
  16. 2026-08-06 12:50 UTCEG score recompute
  17. 2026-08-06 12:50 UTCGHSA enrichment
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-05 14:41 UTCGHSA enrichment
  21. 2026-08-04 16:33 UTCEG score recompute
  22. 2026-08-04 16:33 UTCGHSA enrichment
  23. 2026-08-04 15:19 UTCEG score recompute
  24. 2026-08-04 14:48 UTCEG score recompute
  25. 2026-08-04 14:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67618?
CVE-2026-67618 is a medium vulnerability published on August 4, 2026. 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…
When was CVE-2026-67618 disclosed?
CVE-2026-67618 was first published in the National Vulnerability Database on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67618 actively exploited?
CVE-2026-67618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.0% of all scored CVEs.
What is the CVSS score of CVE-2026-67618?
CVE-2026-67618 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-67618?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67618, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-67618

Explore →

Is Your Infrastructure Affected by CVE-2026-67618?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs