763 matches found
CVE-2026-53765
CVE-2026-53765 / GHSA-3PVJ-JV98-QHJQ affects chrome-devtools-mcp (Chrome DevTools for agents). The vulnerability occurs when the daemon writes its PID file to a deterministic runtime path under /tmp on POSIX systems (macOS or Linux with XDG_RUNTIME_DIR unset). The code uses fs.writeFileSync() wit...
CVE-2026-53765
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...
CVE-2026-53765 chrome-devtools-mcp: daemon.pid write follows symlinks in /tmp fallback runtime directory
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...
EUVD-2026-39105
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...
CVE-2026-53766
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.resolvefilePath textually falls under one of the configured root paths. path.resolve...
CVE-2026-53766 chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots
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.resolvefilePath textually falls under one of the configured root paths. path.resolve...
browser-ipc-cdp (>=2.0.0, <=3.13.0), chrome-devtools-mcp-docker (>=0.1.5, <=0.1.7) +1 more potentially affected by CVE-2026-53766 via chrome-devtools-mcp (0.25.0)
chrome-devtools-mcp NPM version 0.25.0 is affected by a known vulnerability. The following packages have a transitive dependency on chrome-devtools-mcp and may be impacted: - browser-ipc-cdp =2.0.0, =0.1.5, =1.0.1, =1.0.9 Source cves: CVE-2026-53766 Source advisory: MEND:CVE-2026-53766...
DEBIAN-CVE-2026-13025
Race in DevTools in Google Chrome prior to 149.0.7827.197 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. Chromium security severity: High...
CVE-2026-13025
Race in DevTools in Google Chrome prior to 149.0.7827.197 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. Chromium security severity: High...
CVE-2026-13025
Race in DevTools in Google Chrome prior to 149.0.7827.197 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. Chromium security severity: High...
CVE-2026-53765: Improper Link Resolution Before File Access
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...
CVE-2026-53766: Improper Limitation of a Pathname to a Restricted Directory
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.resolvefilePath textually falls under one of the configured root paths. path.resolve...
PT-2026-52106
Name of the Vulnerable Software and Affected Versions chrome-devtools-mcp versions 0.24.0 through 1.0.9 Description A workspace-boundary bypass exists because the McpContext.validatePath function fails to canonicalize symbolic links when checking if a path falls under configured root paths. This...
@liqi0816/chrome-devtools-mcp-rebrowser (>=1.0.0, <=1.0.3), @mallocfeng/chromedev (>=0.1.0, <=0.1.8) +10 more potentially affected by CVE-2026-53765 via chrome-devtools-mcp (>=0.20.3, <=0.25.0)
chrome-devtools-mcp NPM version =0.20.3, =1.0.0, =0.1.0, =0.2.8, =0.2.7, =2.0.0, =0.1.5, =0.1.49, =1.0.5, =1.0.1, =1.0.9 Source cves: CVE-2026-53765 Source advisory: OSV:GHSA-3PVJ-JV98-QHJQ...
NPM: Chrome DevTools for agents: daemon.pid write follows symlinks in /tmp fallback runtime directory
NPM: Chrome DevTools for agents: daemon.pid write follows symlinks in /tmp fallback runtime directory vulnerability discovered by ? in WordPress Npm chrome-devtools-mcp versions = 0.20.0, = 1.0.1...
@liqi0816/chrome-devtools-mcp-rebrowser (>=1.0.0, <=1.0.3), @mallocfeng/chromedev (>=0.1.0, <=0.1.8) +10 more potentially affected by CVE-2026-53765 via chrome-devtools-mcp (>=0.20.3, <=0.25.0)
chrome-devtools-mcp NPM version =0.20.3, =1.0.0, =0.1.0, =0.2.8, =0.2.7, =2.0.0, =0.1.5, =0.1.49, =1.0.5, =1.0.1, =1.0.9 Source cves: CVE-2026-53765 Source advisory: SNYK:JS-CHROMEDEVTOOLSMCP-17391448...
@liqi0816/chrome-devtools-mcp-rebrowser (>=1.0.0, <=1.0.3), @mallocfeng/chromedev (>=0.1.0, <=0.1.8) +10 more potentially affected by CVE-2026-53765 via chrome-devtools-mcp (>=0.20.3, <=0.25.0)
chrome-devtools-mcp NPM version =0.20.3, =1.0.0, =0.1.0, =0.2.8, =0.2.7, =2.0.0, =0.1.5, =0.1.49, =1.0.5, =1.0.1, =1.0.9 Source cves: CVE-2026-53765 Source advisory: GHSA-3PVJ-JV98-QHJQ...
GHSA-3PVJ-JV98-QHJQ Chrome DevTools for agents: daemon.pid write follows symlinks in /tmp fallback runtime directory
Summary 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 $XDGRUNTIMEDIR is unset, that runtime path falls back to /tmp/chrome-devtools-mcp-/daemon.pid. Because the write does not us...
GHSA-RQ7W-G337-39QQ Nuxt: Dev server discloses project absolute path and persistent workspace UUID via `/.well-known/appspecific/com.chrome.devtools.json`
Summary When running nuxt dev, Nuxt registers an unauthenticated route at /.well-known/appspecific/com.chrome.devtools.json that returns the absolute filesystem path of the project root and a per-project UUID persisted to nodemodules/.cache/nuxt/chrome-workspace.json. The route is enabled by...
Exposure of Sensitive System Information to an Unauthorized Control Sphere
Overview Affected versions of this package are vulnerable to Exposure of Sensitive System Information to an Unauthorized Control Sphere via the unauthenticated /.well-known/appspecific/com.chrome.devtools.json endpoint, which exposes the absolute filesystem path of the project and a persistent...