CVE-2026-61647

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Sep 21, 2026
Patch available. Sources: github.
github Patch Available

Path traversal in vault.batch tool allows arbitrary file write outside intended vault directory · Advisory · roomi-fields/notebooklm-mcp · GitHub

https://github.com/roomi-fields/notebooklm-mcp/security/advisories/GHSA-jjhp-8crj-mppq

Vendor Advisories for CVE-2026-61647(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@roomi-fields/notebooklm-mcp—2.0.3—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 8× 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-09-24 16:42 UTCEG score recompute
  2. 2026-09-24 04:37 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 16:22 UTCEG score recompute
  5. 2026-09-22 15:45 UTCEG score recompute
  6. 2026-09-22 09:23 UTCEG score recompute
  7. 2026-09-21 21:17 UTCEG score recompute
  8. 2026-09-21 21:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61647?
CVE-2026-61647 is a high vulnerability published on September 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 batchtovault MCP…
When was CVE-2026-61647 disclosed?
CVE-2026-61647 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61647 actively exploited?
CVE-2026-61647 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 77.3% of all scored CVEs.
What is the CVSS score of CVE-2026-61647?
CVE-2026-61647 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-61647?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61647, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61647

Explore →

Is Your Infrastructure Affected by CVE-2026-61647?

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