Description
NotebookLM MCP is an MCP server and HTTP service for interacting with Google NotebookLM and exporting generated content to local vault directories. Versions 1.6.0 through 2.0.2 contain a path traversal vulnerability in the `POST /batch-to-vault` endpoint, also exposed through the `batch_to_vault` MCP tool beginning in version 1.7.0, because attacker-controlled `vault_dir` and `slug_prefix` values can cause Markdown and JSON files to be written outside the intended vault directory to any location writable by the server process. Version 2.0.3 sanitizes `slug_prefix` and supports vault containment when `NOTEBOOKLM_VAULT_ROOT` is configured; containment is not enabled if that variable is unset. Users unable to upgrade should run the server as a dedicated unprivileged account restricted to the intended vault, keep the HTTP endpoint limited to localhost, and validate `vault_dir` values supplied by LLMs processing untrusted content.
Published: 2026-09-21
Score: 7.1 High
EPSS: n/a
KEV: No
Impact: Arbitrary file write via path traversal
Action: Patch Immediately
AI Analysis

Impact

This vulnerability in the NotebookLM MCP server allows an attacker to craft input to the POST /batch-to-vault endpoint or the batch_to_vault MCP tool such that the supplied vault_dir and slug_prefix fields are not properly sanitized. By exploiting the path traversal logic, the server can write Markdown and JSON files to any location writable by the process, effectively enabling arbitrary file creation or modification outside the intended vault directory.

Affected Systems

The affected product is the roomi-fields notebooklm-mcp server. Versions 1.6.0 through 2.0.2, inclusive, are susceptible. Version 1.7.0 introduced the batch_to_vault tool but remains vulnerable. The vulnerability is fixed starting with version 2.0.3, which sanitizes slug_prefix and enables vault containment when the NOTEBOOKLM_VAULT_ROOT environment variable is set. Clients unable to upgrade should confine the server process to a dedicated unprivileged account and enforce local‑only access.

Risk and Exploitability

The CVSS score of 7.1 classifies this issue as high severity. While an EPSS score is not available, the lack of KEV listing and the fact that the vulnerability requires crafted HTTP requests or tool usage suggest a moderate exploitation probability in realistic settings. If the HTTP service is exposed to untrusted users, an attacker could write arbitrary files, including potentially executable code, thereby achieving privilege escalation or data exfiltration. Limiting network exposure, running a non‑privileged account, and validating supplied paths are essential mitigations against this attack.

Generated by OpenCVE AI on September 21, 2026 at 22:41 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to NotebookLM MCP 2.0.3 or later to apply path sanitization and vault containment.
  • Configure the NOTEBOOKLM_VAULT_ROOT environment variable to enforce containment if upgrading is not possible.
  • Run the NotebookLM MCP server as a dedicated unprivileged account that only has write access to the intended vault directory.
  • Restrict the HTTP endpoint to localhost or secure it behind a firewall so that only trusted internal processes can reach the vulnerable endpoint.
  • Add server‑side validation to reject or sanitize vault_dir and slug_prefix values supplied by LLMs or other untrusted content.

Generated by OpenCVE AI on September 21, 2026 at 22:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 21 Sep 2026 21:15:00 +0000

Type Values Removed Values Added
Description NotebookLM MCP is an MCP server and HTTP service for interacting with Google NotebookLM and exporting generated content to local vault directories. Versions 1.6.0 through 2.0.2 contain a path traversal vulnerability in the `POST /batch-to-vault` endpoint, also exposed through the `batch_to_vault` MCP tool beginning in version 1.7.0, because attacker-controlled `vault_dir` and `slug_prefix` values can cause Markdown and JSON files to be written outside the intended vault directory to any location writable by the server process. Version 2.0.3 sanitizes `slug_prefix` and supports vault containment when `NOTEBOOKLM_VAULT_ROOT` is configured; containment is not enabled if that variable is unset. Users unable to upgrade should run the server as a dedicated unprivileged account restricted to the intended vault, keep the HTTP endpoint limited to localhost, and validate `vault_dir` values supplied by LLMs processing untrusted content.
Title @roomi-fields/notebooklm-mcp has path traversal in vault.batch tool that allows arbitrary file write outside intended vault directory
Weaknesses CWE-22
CWE-73
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-21T21:00:58.673Z

Reserved: 2026-07-10T17:38:57.112Z

Link: CVE-2026-61647

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-21T21:17:07.107

Modified: 2026-09-21T21:17:07.107

Link: CVE-2026-61647

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-21T22:45:17Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-73

    External Control of File Name or Path