CVE-2026-7810
Path Traversal in python-notebook-mcp
Publication date: 2026-05-05
Last updated on: 2026-05-05
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| usamak98 | python-notebook-mcp | to a05a232815809a7e425b5fa7be26e0d4369894c2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a flaw in the UsamaK98 python-notebook-mcp project affecting the functions create_notebook, read_notebook, edit_cell, and add_cell in the file server.py. It allows for path traversal, meaning an attacker can manipulate file paths to access files and directories outside the intended scope.
The attack can be initiated remotely, and an exploit has already been published, making it possible for attackers to use this vulnerability.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to access or manipulate files on the server that should be restricted, potentially leading to unauthorized data access or modification.
Since the exploit is publicly available and the attack can be performed remotely without authentication, it increases the risk of compromise.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthorized remote attackers to perform path traversal, enabling them to read, write, or modify notebook files outside the intended workspace. This can lead to exposure or alteration of sensitive data contained within notebooks, posing high confidentiality and integrity risks.
Such unauthorized access and manipulation of potentially sensitive information could lead to non-compliance with data protection regulations like GDPR and HIPAA, which require strict controls over the confidentiality and integrity of personal and health-related data.
Mitigations such as restricting service access to trusted users, minimizing filesystem privileges, and isolating the service environment are recommended to reduce the risk of data breaches and help maintain compliance.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves path traversal in the python-notebook-mcp server, allowing unauthorized access to files outside the intended workspace. Detection can focus on monitoring for suspicious path traversal payloads in requests to the MCP service, such as usage of '../' sequences or absolute paths in notebook manipulation commands.
Since the attack requires invoking notebook MCP tools remotely, network detection can include inspecting traffic to the MCP server for unusual file path parameters.
Suggested commands to detect exploitation attempts or suspicious activity include searching server logs or monitoring network traffic for traversal patterns:
- grep -r "\.\./" /path/to/python-notebook-mcp/logs
- tcpdump -A -s 0 port <MCP_server_port> | grep -E "\.\./|/absolute/path"
- Audit filesystem access for unexpected reads/writes outside the workspace directory.
Additionally, static code analysis tools like CodeQL were used to discover this vulnerability, so running similar scans on your codebase or server scripts might help identify vulnerable code patterns.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the MCP service to trusted users only and minimizing filesystem privileges granted to the MCP server process.
Using containerization or chroot-like isolation can help contain the MCP server and prevent it from accessing files outside the intended workspace.
Until an official fix is released, avoid exposing the MCP server to untrusted networks and monitor for suspicious activity.
The recommended fix involves canonicalizing paths, enforcing workspace boundaries, blocking traversal segments, and adding regression tests to prevent exploitation.