{"answers":{"affected":"2 open source packages ship an affected version, including chrome-devtools-mcp. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53766 exists.","fix":"Upgrade chrome-devtools-mcp to 1.1.0 or later.","what":"CVE-2026-53766 is a medium-severity path traversal vulnerability in ChromeDevTools chrome-devtools-mcp, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53766 and fix it if it is affected.\n\nWhat it is: CVE-2026-53766 is a medium-severity path traversal vulnerability in ChromeDevTools chrome-devtools-mcp, published on 24 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53766 exists.\n\nAffected packages and fixed versions:\n- chrome-devtools-mcp (npm): affected from 0.24.0; fixed in 1.1.0\n- chrome-devtools-mcp (npm): affected from 0.24.0; fixed in 1.1.0\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-53766/ (Markdown: https://insights.sbomify.com/CVE-2026-53766/index.md)","id":"CVE-2026-53766","markdown":"https://insights.sbomify.com/CVE-2026-53766/index.md","name":"CVE-2026-53766","record":{"aliases":["GHSA-8qf9-62x2-82pp"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Chrome DevTools MCP","requires_auth":"low_privilege","summary":"Attackers can bypass workspace restrictions to read or write files outside the allowed directory via symlink manipulation in Chrome DevTools MCP.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"chrome-devtools-mcp","vendor":"google"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textually falls under one of the configured root paths. path.resolve() does not canonicalize symbolic links. As a result, a symlink inside a configured workspace root can point to a file outside that root, pass validation, and then be followed by downstream file read/write operations. This bypass applies even when the MCP client correctly declares the roots capability with a non-empty list. It is separate from the documented legacy behavior where missing roots capability allows all paths. The practical impact is a workspace-boundary bypass. In the write direction, filePath-writing tools can overwrite out-of-root files through an in-root symlink. In the read direction, upload_file can read through the symlink and send the file to the currently selected web page. This vulnerability is fixed in 1.1.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots","id":"CVE-2026-53766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Avo: Direct attachment upload endpoint lacks upload authorization and bypasses field-level upload policy","id":"CVE-2026-53769"},"packages":[{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0.24.0"],"last_affected":[],"package":"chrome-devtools-mcp","purl":null,"source":"GHSA-8qf9-62x2-82pp"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0.24.0"],"last_affected":[],"package":"chrome-devtools-mcp","purl":"pkg:npm/chrome-devtools-mcp","source":"GHSA-8qf9-62x2-82pp"}],"prev":{"headline":"chrome-devtools-mcp: daemon.pid write follows symlinks in /tmp fallback runtime directory","id":"CVE-2026-53765"},"products":["chrome-devtools-mcp"],"published":"2026-06-24","related":[{"cvss_score":6.1,"headline":"chrome-devtools-mcp: daemon.pid write follows symlinks in /tmp fallback runtime directory","id":"CVE-2026-53765","kev_date_added":null,"published":"2026-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-06-25","vendors":["ChromeDevTools"]},"summary":"Attackers can bypass workspace restrictions to read or write files outside the allowed directory via symlink manipulation in Chrome DevTools MCP.","url":"https://insights.sbomify.com/CVE-2026-53766/"}