@puchunjie/doc-tools-mcp has a Path Traversal Issue
CVE-2026-7738 · GHSA-gcmm-c94j-j47x · published 2026-05-04 · updated 2026-05-08
- Severity
- Low
- CVSS score
- 6.3
- Chance of exploitation (EPSS)
- 0.34%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
A security flaw has been discovered in puchunjie doc-tools-mcp 1.0.18. This affects the function create_document/open_document of the file src/mcp-server.ts of the component MCP Interface. The manipulation of the argument filePath results in path traversal. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
No fixed release is listed yet for @puchunjie/doc-tools-mcp. Follow the source advisory for updates, and until one ships:
General guidance from ShieldPi, not a vendor fix
- Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @puchunjie/doc-tools-mcp | npm | <= 1.0.18 | No fix yet |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.