{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9468 exists.","fix":"No fix has been published for CVE-2026-9468 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9468 is a medium-severity path traversal vulnerability in dazeb cline-mcp-memory-bank, published on 25 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9468 and fix it if it is affected.\n\nWhat it is: CVE-2026-9468 is a medium-severity path traversal vulnerability in dazeb cline-mcp-memory-bank, published on 25 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9468 exists.\n\nAffected product: dazeb cline-mcp-memory-bank. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-9468/ (Markdown: https://insights.sbomify.com/CVE-2026-9468/index.md)","id":"CVE-2026-9468","markdown":"https://insights.sbomify.com/CVE-2026-9468/index.md","name":"CVE-2026-9468","record":{"aliases":["GHSA-2fh4-hw94-qg7r"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MCP memory bank library","requires_auth":"low_privilege","summary":"Remote attackers can exploit path traversal in the memory bank initialization to read or modify arbitrary files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"dazeb cline-mcp-memory-bank index.ts handleInitializeMemoryBank path traversal","id":"CVE-2026-9468","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"yashpokharna2555 StudentManagementSystem success.php sql injection","id":"CVE-2026-9469"},"packages":[],"prev":{"headline":"debugmcp mcp-debugger server.ts handleGetSourceContext path traversal","id":"CVE-2026-9467"},"products":["cline-mcp-memory-bank"],"published":"2026-05-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-26","vendors":["dazeb"]},"summary":"Remote attackers can exploit path traversal in the memory bank initialization to read or modify arbitrary files.","url":"https://insights.sbomify.com/CVE-2026-9468/"}