dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-9468

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-25
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 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.

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 the handleInitializeMemoryBank function within src/index.ts of the dazeb cline-mcp-memory-bank project. The projectPath argument is not properly validated, allowing an attacker to manipulate it with sequences like ../ to access files and directories outside the intended memory bank directory. This could enable unauthorized file read/write operations on the host system.

MitigationImplement strict input validation on the projectPath parameter using path canonicalization (path.resolve()) combined with bounds checking to ensure the resolved path remains within the intended base directory. Reject any input containing path traversal sequences or that resolves outside allowed boundaries.

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. Identify installed cline-mcp-memory-bank version
    Run 'npm list cline-mcp-memory-bank' or check package.json for the version field
    Affected if Version is unknown or earlier than any patched version that addresses path traversal in handleInitializeMemoryBank
  2. Locate handleInitializeMemoryBank function in source
    Inspect src/index.ts file and search for the handleInitializeMemoryBank function definition
    Affected if The function exists and accepts a projectPath parameter without proper path validation
  3. Check projectPath parameter validation
    Examine the function body for sanitization logic - look for path canonicalization (e.g., path.resolve, path.normalize) and boundary checking that ensures the resolved path stays within the intended base directory
    Affected if No validation, sanitization, or canonicalization of projectPath is performed before using it in file operations
  4. Verify if memory bank feature is enabled
    Check if the memory bank functionality is actively used or exposed via API/endpoints in your deployment
    Affected if The handleInitializeMemoryBank function is accessible and projectPath can be supplied by users
  5. Test for path traversal vulnerability
    If the function is accessible, attempt to pass a projectPath containing traversal sequences (e.g., ../../etc) and observe if files outside the intended directory are accessible or created
    Affected if Path traversal sequences are accepted and result in access to files outside the intended memory bank directory

You are affected if cline-mcp-memory-bank is installed with handleInitializeMemoryBank exposed, and the projectPath parameter lacks proper validation allowing ../ sequences to escape the intended directory.

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 projectPath parameter using path canonicalization (path.resolve()) combined with bounds checking to ensure the resolved path remains within the intended base directory. Reject any input containing path traversal sequences or that resolves outside allowed boundaries.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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