dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7738

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability exists in puchunjie doc-tools-mcp 1.0.18 within the MCP Interface (src/mcp-server.ts) in the create_document and open_document functions. The filePath argument is not properly validated, allowing attackers to use manipulation techniques like '../' sequences to access files outside the intended directory.

MitigationImplement strict input validation on the filePath parameter to reject paths containing traversal sequences (../) and enforce allowlisting of permitted directories; use path canonicalization to resolve and validate the final resolved path before file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify doc-tools-mcp installation and version
    Run 'npm list doc-tools-mcp' or check package.json dependencies to confirm the installed version of doc-tools-mcp
    Affected if The installed version is 1.0.18 or falls within the 1.0.x range before a fix is applied
  2. Confirm MCP server is running with vulnerable functions exposed
    Inspect the running MCP server configuration and confirm that src/mcp-server.ts is loaded and the create_document and open_document functions are exposed via the MCP interface
    Affected if The MCP server is active and these functions are accessible to clients
  3. Identify if external input reaches the filePath parameter
    Review application logs or network traffic to determine whether untrusted user input can be passed to the create_document or open_document functions through the MCP interface
    Affected if User-supplied paths can reach these functions without validation
  4. Test for path traversal vulnerability
    Attempt to invoke create_document or open_document with a filePath containing '../' sequences (for example, '../../../etc/passwd') through the MCP interface API
    Affected if The application accepts and processes paths containing traversal sequences without rejecting them
  5. Check if directory allowlisting or path validation is implemented
    Examine the src/mcp-server.ts file or runtime configuration to see if there is validation that restricts filePath to an allowed directory list or uses path canonicalization
    Affected if No path validation or allowlisting is present, or the validation can be bypassed

A user is affected if they are running doc-tools-mcp version 1.0.18 with the MCP server exposing create_document or open_document functions that accept unvalidated user input for the filePath parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the filePath parameter to reject paths containing traversal sequences (../) and enforce allowlisting of permitted directories; use path canonicalization to resolve and validate the final resolved path before file operations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7738 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data