{"answers":{"affected":"2 open source packages ship an affected version, including @puchunjie/doc-tools-mcp.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7738 exists.","fix":"No fix has been published for CVE-2026-7738 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7738 is a medium-severity path traversal vulnerability in puchunjie doc-tools-mcp, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7738 and fix it if it is affected.\n\nWhat it is: CVE-2026-7738 is a medium-severity path traversal vulnerability in puchunjie doc-tools-mcp, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7738 exists.\n\nAffected packages and fixed versions:\n- @puchunjie/doc-tools-mcp (npm): affected all versions up to 1.0.18; no fix listed\n- @puchunjie/doc-tools-mcp (npm): affected all versions up to 1.0.18; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-7738/ (Markdown: https://insights.sbomify.com/CVE-2026-7738/index.md)","id":"CVE-2026-7738","markdown":"https://insights.sbomify.com/CVE-2026-7738/index.md","name":"CVE-2026-7738","record":{"aliases":["GHSA-gcmm-c94j-j47x"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP document tools","requires_auth":"low_privilege","summary":"Attackers can exploit path traversal in the MCP server to read or modify arbitrary files via manipulated file paths.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"puchunjie doc-tools-mcp MCP mcp-server.ts open_document path traversal","id":"CVE-2026-7738","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"justdan96 tsMuxer hevc.cpp setFPS denial of service","id":"CVE-2026-7739"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.18"],"package":"@puchunjie/doc-tools-mcp","purl":null,"source":"GHSA-gcmm-c94j-j47x"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.0.18"],"package":"@puchunjie/doc-tools-mcp","purl":"pkg:npm/%40puchunjie/doc-tools-mcp","source":"GHSA-gcmm-c94j-j47x"}],"prev":{"headline":"osrg GoBGP BMP Parser bmp.go BMPStatisticsReport.ParseBody out-of-bounds","id":"CVE-2026-7737"},"products":["doc-tools-mcp"],"published":"2026-05-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-05","vendors":["puchunjie"]},"summary":"Attackers can exploit path traversal in the MCP server to read or modify arbitrary files via manipulated file paths.","url":"https://insights.sbomify.com/CVE-2026-7738/"}