CVE-2026-53765

{"id": "CVE-2026-53765", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-53765", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-26T17:51:05.310554Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.1, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 4.2, "exploitabilityScore": 1.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "ChromeDevTools", "product": "chrome-devtools-mcp", "versions": [{"status": "affected", "version": ">= 0.20.0, < 1.1.0"}]}]}], "published": "2026-06-24T22:16:47.783", "references": [{"url": "https://github.com/ChromeDevTools/chrome-devtools-mcp/security/advisories/GHSA-3pvj-jv98-qhjq", "tags": ["Exploit", "Third Party Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-59"}]}], "descriptions": [{"lang": "en", "value": "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-<uid>/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-<victim_uid>/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."}, {"lang": "es", "value": "Chrome DevTools para agentes (chrome-devtools-mcp) permite a su agente de codificaci\u00f3n controlar e inspeccionar un navegador Chrome en vivo. Desde 0.20.0 hasta 1.1.0, el demonio chrome-devtools-mcp escribe su archivo PID con fs.writeFileSync() en una ruta de tiempo de ejecuci\u00f3n determinista. En entornos macOS t\u00edpicos, y en sesiones de Linux donde $XDG_RUNTIME_DIR no est\u00e1 configurado, esa ruta de tiempo de ejecuci\u00f3n recurre a /tmp/chrome-devtools-mcp-[uid]/daemon.pid. Debido a que la escritura no utiliza O_NOFOLLOW, un usuario local de bajos privilegios en el mismo host POSIX puede pre-crear /tmp/chrome-devtools-mcp-[victim_uid]/daemon.pid como un enlace simb\u00f3lico a un archivo escribible por la v\u00edctima. Cuando la v\u00edctima inicia m\u00e1s tarde el modo demonio, fs.writeFileSync() sigue el enlace simb\u00f3lico y trunca el archivo objetivo a la cadena PID del demonio. Esta vulnerabilidad est\u00e1 corregida en 1.1.0."}], "lastModified": "2026-10-25T23:10:00.167", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:google:chrome-devtools-mcp:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "ECCAC380-0C97-4614-B8EF-18B0BEA5CFA5", "versionEndExcluding": "1.1.0", "versionStartIncluding": "0.20.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}