# Safe Codex Prompt: CVE-2026-61647

Prepare a defensive remediation plan for CVE-2026-61647.

Use only the public-safe context below unless the user separately provides repo context.

Source summary: NVD: NotebookLM MCP is an MCP server and HTTP service for interacting with Google NotebookLM and exporting generated content to local vault directories. NVD: 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... NVD: 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.
Affected vendor/product: unknown / unknown
Risk context: {'severity': 'HIGH', 'cvss_score': 7.1, 'cvss_label': 'HIGH', 'epss_percentile': None, 'kev_status': 'not_listed', 'risk_flags': ['CVSS HIGH', 'official reference present']}
Remediation context: {'recommended_route': 'vendor_patch_or_mitigation', 'reference_status': 'official_reference_present', 'patch_status': 'requires_confirmation', 'fixed_versions': [], 'mitigation_notes': ['Remediation reference present; patch status requires confirmation in the linked advisory.', 'Patch status requires confirmation from the linked advisory or official source.']}

Human checklist:
- Confirm whether the listed product or package is present.
- Confirm affected version.
- Review vendor advisory or official source.
- Confirm patch, fixed version, mitigation, workaround, or monitor-only decision.
- Confirm exposure.
- Document remediation status.

Allowed actions:
- summarize vendor guidance
- prepare a defensive remediation plan
- identify affected dependencies only when repo context is separately provided by the user
- suggest tests and validation steps
- document human verification questions

Disallowed actions:
- generate offensive code
- provide payloads
- scan external targets
- change production systems
- merge or deploy changes
- create GitHub issues or pull requests without explicit separate approval

Acceptance criteria:
- Affected product or dependency presence is confirmed by a human.
- Affected version is confirmed or marked not applicable.
- Official advisory or source reference is reviewed.
- Patch, fixed version, mitigation, workaround, or monitor-only decision is documented.
- Validation steps are proposed without external scanning or production mutation.

You may prepare a defensive remediation plan.
You may summarize vendor guidance.
You may identify affected dependencies only if repo context is separately provided by the user.
You may suggest tests and validation steps.
You must not generate offensive code.
You must not provide payloads.
You must not scan external targets.
You must not change production systems.
You must not merge or deploy.
Human approval is required.