Skip to main content
VulnerabilityPublished

CVE-2026-7445: ZachHandley ZMCPTools · Path Traversal

Source GCVE Database

0
Authoritative record:CVE-2026-7445· Medium 5.3

Public exploit available · CVSS 5.3 Medium.

Data as of 27 Oct 2026, 00:08 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ZachHandleyZMCPToolsAffected
  • =0.2.0
  • =0.2.1
  • =0.2.2
Fixed in–
GitHubzachhandley/ZMCPToolspkg:github/zachhandley/ZMCPToolsOther threatsAffected
  • =0.2.0
  • =0.2.1
  • =0.2.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor the project for updates and consider implementing temporary controls such as input validation or restricting access to the vulnerable component until a patch is released. Avoid exposing the affected functionality to untrusted networks if possible.

Description

A path traversal vulnerability exists in ZachHandley ZMCPTools up to version 0.2.2 in the MCP Log Resource Handler component. The flaw involves improper handling of the dirname argument in the src/managers/ResourceManager.ts file, allowing remote attackers to manipulate file paths. The vulnerability has a CVSS score of 6.3 (medium severity) and has been publicly disclosed. No patch or vendor response has been reported yet.

References

Community reviews

Loading reviews…