{"answers":{"affected":"2 open source packages ship an affected version, including chrome-devtools-mcp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53765 in the wild and no public exploit code.","fix":"Upgrade chrome-devtools-mcp to 1.1.0 or later.","what":"CVE-2026-53765 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-53765 and fix it if it is affected.\n\nWhat it is: CVE-2026-53765 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: There is no known exploitation of CVE-2026-53765 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- chrome-devtools-mcp (npm): affected from 0.20.0; fixed in 1.1.0\n- chrome-devtools-mcp (npm): affected from 0.20.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-53765/ (Markdown: https://insights.sbomify.com/CVE-2026-53765/index.md)","id":"CVE-2026-53765","markdown":"https://insights.sbomify.com/CVE-2026-53765/index.md","name":"CVE-2026-53765","record":{"aliases":["GHSA-3pvj-jv98-qhjq"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Chrome DevTools MCP","requires_auth":"low_privilege","summary":"A local attacker can overwrite arbitrary files via symlink attacks on the daemon PID file in the temporary directory.","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"}],"description":"Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.20.0 until 1.1.0, The chrome-devtools-mcp daemon writes its PID file with fs.writeFileSync() to a deterministic runtime path. On typical macOS environments, and on Linux sessions where $XDG_RUNTIME_DIR is unset, that runtime path falls back to /tmp/chrome-devtools-mcp-\u003cuid\u003e/daemon.pid. Because the write does not use O_NOFOLLOW, a local low-privilege user on the same POSIX host can pre-create /tmp/chrome-devtools-mcp-\u003cvictim_uid\u003e/daemon.pid as a symlink to a file writable by the victim. When the victim later starts daemon mode, fs.writeFileSync() follows the symlink and truncates the target file to the daemon PID string. 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":"none_known"},"has_fix":true,"headline":"chrome-devtools-mcp: daemon.pid write follows symlinks in /tmp fallback runtime directory","id":"CVE-2026-53765","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":"chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots","id":"CVE-2026-53766"},"packages":[{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0.20.0"],"last_affected":[],"package":"chrome-devtools-mcp","purl":null,"source":"GHSA-3pvj-jv98-qhjq"},{"ecosystem":"npm","fixed":["1.1.0"],"introduced":["0.20.0"],"last_affected":[],"package":"chrome-devtools-mcp","purl":"pkg:npm/chrome-devtools-mcp","source":"GHSA-3pvj-jv98-qhjq"}],"prev":{"headline":"OP-TEE has AES-GCM 32-bit integer overflow in length counters that breaks authentication guarantee","id":"CVE-2026-53763"},"products":["chrome-devtools-mcp"],"published":"2026-06-24","related":[{"cvss_score":6.1,"headline":"chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots","id":"CVE-2026-53766","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["ChromeDevTools"]},"summary":"A local attacker can overwrite arbitrary files via symlink attacks on the daemon PID file in the temporary directory.","url":"https://insights.sbomify.com/CVE-2026-53765/"}