@roomi-fields/notebooklm-mcp has a path traversal in vault.batch tool that allows arbitrary file write outside intended vault directory

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · 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 · score source

EPSS

• CVE-2026-61647: 0.44% estimated exploitation activity in the next 30 days; percentile 38.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The vaultbatch MCP tool (and the equivalent POST /batch-to-vault HTTP endpoint) accepted a caller-supplied vaultdir path that was passed directly to path.resolve() + fs.mkdir() with no containment check. A caller — or a prompt-injected LLM driving the MCP — could therefore create directories and write .md / .json answer files anywhere the server process can write. The slugprefix parameter had a parallel, smaller traversal vector: it was concatenated into the filename without sanitization, so a prefix containing / or .. could escape the resolved vault directory through the filename component. Impact File write (markdown + JSON sidecars) to any location writable by the server process. The written files are inert content (no code execution by themselves), but in a multi-user context — or when the MCP server is driven by an LLM that has read untrusted content (prompt injection) — this allows an attacker to plant files in sensitive locations (autostart folders, shell startup…

Published by the source

22 Sep 2026, 14:43 UTC

Last modified by the source

22 Sep 2026, 15:00 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jjhp-8crj-mppq

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-jjhp-8crj-mppq

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-jjhp-8crj-mppq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61647

Advisory: @roomi-fields/notebooklm-mcp has a path traversal in vault.batch tool that allows arbitrary file write outside intended vault directory
IDs: CVE-2026-61647, GHSA-jjhp-8crj-mppq
Record: https://patchnext.com/advisories/cve-2026-61647 (revision 4, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @roomi-fields/notebooklm-mcp 2.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @roomi-fields/notebooklm-mcp: affected >= 1.6.0, < 2.0.3; fixed in 2.0.3

## Suggested inspection (read-only)
- `npm ls @roomi-fields/notebooklm-mcp --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @roomi-fields/notebooklm-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jjhp-8crj-mppq (GitHub-reviewed advisory GHSA-jjhp-8crj-mppq lists affected ranges: npm @roomi-fields/notebooklm-mcp >=1.6.0 <2.0.3)
- Verified: https://osv.dev/vulnerability/GHSA-jjhp-8crj-mppq (OSV record GHSA-jjhp-8crj-mppq lists affected ranges: npm @roomi-fields/notebooklm-mcp >=1.6.0 <2.0.3 (fixed))

Commands are suggestions: review each one before running it.