CVE-2026-67618: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-v9v8-jp27-55gf
Share
CVSS 6.5
CWE-345
Published
Advisory Summary

CVE-2026-67618 is a HIGH (CVSS 6.5) security vulnerability vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-67618 at a Glance

CVE Identifier CVE-2026-67618
GHSA Identifier GHSA-v9v8-jp27-55gf
Severity HIGH
CVSS v3.1 Base Score 6.5
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-67618

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-67618, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-67618 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-67618
Software Source Repository REPOSITORY
https://github.com/marimo-team/marimo/pull/10281
Security Fix Commit FIX COMMIT
https://github.com/marimo-team/marimo/commit/1a21bd71e258438d2511136b5edacc94c08855f4
Software Release RELEASE
https://github.com/marimo-team/marimo/releases/tag/0.23.15
www.vulncheck.com/advisories/marimo-a... WEB
https://www.vulncheck.com/advisories/marimo-api-key-exfiltration-via-malicious-notebook-pep-723-metadata

Frequently Asked Questions

What is CVE-2026-67618?
CVE-2026-67618 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-345: Insufficient Verification of Data Authenticity.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-67618?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-67618?
CVE-2026-67618 has a CVSS v3.1 base score of 6.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-67618?
CVE-2026-67618 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check Maven dependencies for CVE-2026-67618?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v9v8-jp27-55gf",
  "modified" : "2026-08-04T15:32:24Z",
  "published" : "2026-08-04T15:32:24Z",
  "aliases" : [ "CVE-2026-67618" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-67618"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/marimo-team/marimo/pull/10281"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/marimo-team/marimo/commit/1a21bd71e258438d2511136b5edacc94c08855f4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/marimo-team/marimo/releases/tag/0.23.15"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/marimo-api-key-exfiltration-via-malicious-notebook-pep-723-metadata"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-04T15:16:41Z"
  }
}