Answer in brief
CVE-2026-61647 records a High severity (CVSS 7.1) vulnerability in @roomi-fields/notebooklm-mcp has path traversal in vault.batch tool that allows arbitrary file write outside intended vault directory. The current sources do not mark it as known exploited. The current feed maps roomi-fields/notebooklm-mcp (generic), @roomi-fields/notebooklm-mcp (npm), @roomi-fields/notebooklm-mcp (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps roomi-fields/notebooklm-mcp (generic), @roomi-fields/notebooklm-mcp (npm), @roomi-fields/notebooklm-mcp (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| roomi-fields/notebooklm-mcpgeneric | >=1.6.0 <2.0.3 | 2.0.3 |
| @roomi-fields/notebooklm-mcpnpm | >=1.6.0,<2.0.3 | 2.0.3 |
| @roomi-fields/notebooklm-mcpnpm | >=1.6.0 <2.0.3 | 2.0.3 |
Published upstream
Sep 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.