EUVD-2026-31699
GHSA-2fh4-hw94-qg7r
Severity by source
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
A security flaw has been discovered in dazeb cline-mcp-memory-bank up to 55c81b9cf6c16700983c84dc4cdea3cafa19a75f. The affected element is the function handleInitializeMemoryBank of the file src/index.ts. The manipulation of the argument projectPath results in path traversal. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
AnalysisAI
Path traversal in dazeb cline-mcp-memory-bank exposes host filesystems to authenticated remote attackers via unsanitized user input in the handleInitializeMemoryBank function of src/index.ts. All versions up to and including commit 55c81b9cf6c16700983c84dc4cdea3cafa19a75f are affected, covering the entire release history of this rolling-release MCP memory tool. A public proof-of-concept exploit exists via the project's GitHub issue tracker, though EPSS scoring (0.04%, 13th percentile) and SSVC's non-automatable classification suggest limited mass exploitation risk at time of analysis.
Technical ContextAI
cline-mcp-memory-bank is a Model Context Protocol (MCP) memory bank integration designed for the Cline AI coding assistant, providing a filesystem-backed persistence layer for AI context and project memory. The vulnerable function handleInitializeMemoryBank in src/index.ts accepts a caller-supplied projectPath argument and passes it to filesystem operations without proper sanitization, path normalization, or canonicalization against a safe base directory. This is a textbook CWE-22 (Path Traversal) root cause: ../ sequences or absolute path prefixes in the input traverse outside the intended project directory tree, reaching arbitrary host filesystem paths. The CPE identifier cpe:2.3:a:dazeb:cline-mcp-memory-bank:*:*:*:*:*:*:*:* - with wildcard version - confirms the entire product is affected with no version-based exclusions possible.
RemediationAI
No vendor-released patch has been identified at time of analysis - the project maintainer had not responded to the responsible disclosure as of the time this CVE was reported. Users should monitor the upstream repository at https://github.com/dazeb/cline-mcp-memory-bank/ for a commit adding path canonicalization or input validation to src/index.ts. As compensating controls: restrict which authenticated users or MCP clients are permitted to invoke handleInitializeMemoryBank, specifically rejecting projectPath values containing ../, ..\, encoded traversal sequences (%2e%2e), or absolute path prefixes outside the intended root - note this requires application-layer filtering, not just network-layer controls. Alternatively, disable the memory bank initialization feature entirely if not operationally required. Running the MCP server process inside a container or sandbox with filesystem access restricted to the intended working directory via read-only bind mounts will limit the blast radius of a successful traversal, though it does not eliminate the vulnerability. The VulDB advisory is at https://vuldb.com/vuln/365449.
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today