dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7445

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-30
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 vulnerability has been detected in ZachHandley ZMCPTools up to 0.2.2. Affected by this issue is some unknown functionality of the file src/managers/ResourceManager.ts of the component MCP Log Resource Handler. The manipulation of the argument dirname leads to path traversal. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. 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 · moderate confidence

Path traversal vulnerability in ZMCPTools ResourceManager.ts MCP Log Resource Handler. The dirname argument is not properly sanitized, allowing attackers to manipulate file paths using '../' sequences to access files outside the intended directory. This enables remote attackers to read arbitrary files on the system.

MitigationImplement strict input validation on the dirname parameter - validate that the path resolves within an expected base directory and reject any path containing directory traversal sequences ('../' or '..\'). Alternatively, use path normalization and comparison against an allowed base directory.

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. Locate ZMCPTools installation
    Search for ZMCPTools directories or check npm/yarn/pip packages: 'find / -name "zmcp*" -o -name "*zmcp*" 2>/dev/null' or 'npm list zmcp' / 'pip list | grep -i zmcp'
    Affected if ZMCPTools is not found on the system (not affected)
  2. Identify ZMCPTools version
    Check package.json, requirements.txt, or run 'npm list zmcp-tools' / 'pip show zmcp-tools' to get the installed version
    Affected if Unable to determine version and MCP Log Resource Handler is in use; compare against any known affected versions if available
  3. Verify MCP Log Resource Handler is enabled
    Check ZMCPTools configuration files (e.g., config.json, .zmcprc, or environment variables) for 'MCP' or 'LogResourceHandler' settings; inspect the ResourceManager.ts file to see if LogResourceHandler is imported and instantiated
    Affected if The Log Resource Handler module is loaded or configured in the ZMCPTools setup
  4. Inspect ResourceManager.ts for vulnerable dirname handling
    Locate ResourceManager.ts in the ZMCPTools source (typically in src/ or lib/ directories) and search for the Log Resource Handler code; look for path concatenation using dirname without sanitization, specifically patterns like 'path.join(dirname, ...)' or direct string concatenation with user-controlled dirname
    Affected if The code shows dirname used directly in file path operations without validation (e.g., no check for '../' sequences)
  5. Check if external input reaches the dirname parameter
    Review the API endpoints or functions that accept the dirname argument in ZMCPTools; trace the data flow from HTTP requests, CLI arguments, or configuration to the ResourceManager.ts Log Resource Handler; verify if user-supplied values can reach the vulnerable function
    Affected if External or user-controlled input can be passed as the dirname argument to the Log Resource Handler

You are affected if ZMCPTools is installed with the MCP Log Resource Handler enabled and the dirname parameter in ResourceManager.ts can accept unsanitized user input containing path traversal sequences.

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 dirname parameter - validate that the path resolves within an expected base directory and reject any path containing directory traversal sequences ('../' or '..\'). Alternatively, use path normalization and comparison against an allowed base directory.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7445 — 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-7445 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