NotebookLM MCP 2.0.3 Restricts Vault File Writes
Tech GuruQuick Answer
The authority published GHSA-jjhp-8crj-mppq for @roomi-fields/notebooklm-mcp 1.6.0 through 2.0.2 vault batch workflows. The project fixed path traversal through vault_dir and slug_prefix that could write Markdown and JSON files outside the intended vault. Version 2.0.3 preserves unrestricted legacy behavior when NOTEBOOKLM_VAULT_ROOT is unset, so operators must configure that variable to enable containment. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory @roomi-fields/notebooklm-mcp 1.6.0 through 2.0.2 vault batch workflows, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-09-22 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | @roomi-fields/notebooklm-mcp 1.6.0 through 2.0.2 vault batch workflows |
|---|---|
| Advisory | GHSA-jjhp-8crj-mppq |
| CVE | CVE-2026-61647 |
| Authoritative release date | 2026-09-22 14:43:26 UTC |
| Authority revision date | 2026-09-22 14:43:27 UTC |
| Affected versions | @roomi-fields/notebooklm-mcp versions 1.6.0 through 2.0.2 using vault_batch or POST /batch-to-vault. |
| Fixed version | @roomi-fields/notebooklm-mcp 2.0.3 with NOTEBOOKLM_VAULT_ROOT configured to the intended vault root |
| CVSS base score | 7.1 (CVSS v4.0) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The project fixed path traversal through vault_dir and slug_prefix that could write Markdown and JSON files outside the intended vault. Version 2.0.3 preserves unrestricted legacy behavior when NOTEBOOKLM_VAULT_ROOT is unset, so operators must configure that variable to enable containment.
What To Validate Now
- Inventory. Locate @roomi-fields/notebooklm-mcp 1.6.0 through 2.0.2 vault batch workflows deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: @roomi-fields/notebooklm-mcp versions 1.6.0 through 2.0.2 using vault_batch or POST /batch-to-vault. Do not infer applicability from product family or severity alone.
- Remediate. Apply @roomi-fields/notebooklm-mcp 2.0.3 with NOTEBOOKLM_VAULT_ROOT configured to the intended vault root through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
