CVE-2026-53765: CWE-59: Improper Link Resolution Before File Access ('Link Following') in ChromeDevTools chrome-devtools-mcp
A vulnerability in chrome-devtools-mcp versions from 0.20.0 up to but not including 1.1.0 allows a local low-privilege user to exploit improper link resolution when the daemon writes its PID file. This can lead to truncation of arbitrary files writable by the victim user. The issue is fixed starting from version 1.1.0.
AI Analysis
Technical Summary
The chrome-devtools-mcp daemon writes its PID file to a deterministic runtime path using fs.writeFileSync() without the O_NOFOLLOW flag. On macOS and Linux environments where $XDG_RUNTIME_DIR is unset, this path defaults to /tmp/chrome-devtools-mcp-<uid>/daemon.pid. A local attacker can pre-create this PID file as a symbolic link to a file writable by the victim user. When the daemon starts, it follows the symlink and overwrites the target file with the daemon's PID, causing unintended file truncation. This is a CWE-59 (Improper Link Resolution Before File Access) vulnerability. The vulnerability is fixed in version 1.1.0.
Potential Impact
A local low-privilege user on the same POSIX host can cause the chrome-devtools-mcp daemon to truncate arbitrary files writable by the victim user by exploiting symbolic link following during PID file creation. This can lead to data loss or corruption of victim files. There is no confidentiality impact, but integrity is affected, and availability impact is low.
Mitigation Recommendations
Upgrade chrome-devtools-mcp to version 1.1.0 or later where this vulnerability is fixed. Patch status is not explicitly confirmed in the advisory, but the fix is stated to be in version 1.1.0. Until upgrading, restrict local user access to the /tmp directory or the runtime path to prevent symlink creation by untrusted users.
CVE-2026-53765: CWE-59: Improper Link Resolution Before File Access ('Link Following') in ChromeDevTools chrome-devtools-mcp
Description
A vulnerability in chrome-devtools-mcp versions from 0.20.0 up to but not including 1.1.0 allows a local low-privilege user to exploit improper link resolution when the daemon writes its PID file. This can lead to truncation of arbitrary files writable by the victim user. The issue is fixed starting from version 1.1.0.
CVSS v3.1
Score 6.1medium
Affected software
pkg:github/chromedevtools/chrome-devtools-mcpRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The chrome-devtools-mcp daemon writes its PID file to a deterministic runtime path using fs.writeFileSync() without the O_NOFOLLOW flag. On macOS and Linux environments where $XDG_RUNTIME_DIR is unset, this path defaults to /tmp/chrome-devtools-mcp-<uid>/daemon.pid. A local attacker can pre-create this PID file as a symbolic link to a file writable by the victim user. When the daemon starts, it follows the symlink and overwrites the target file with the daemon's PID, causing unintended file truncation. This is a CWE-59 (Improper Link Resolution Before File Access) vulnerability. The vulnerability is fixed in version 1.1.0.
Potential Impact
A local low-privilege user on the same POSIX host can cause the chrome-devtools-mcp daemon to truncate arbitrary files writable by the victim user by exploiting symbolic link following during PID file creation. This can lead to data loss or corruption of victim files. There is no confidentiality impact, but integrity is affected, and availability impact is low.
Mitigation Recommendations
Upgrade chrome-devtools-mcp to version 1.1.0 or later where this vulnerability is fixed. Patch status is not explicitly confirmed in the advisory, but the fix is stated to be in version 1.1.0. Until upgrading, restrict local user access to the /tmp directory or the runtime path to prevent symlink creation by untrusted users.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-10T17:48:40.547Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c501d4853345fc1e45bc8
Added to database: 06/24/2026, 21:46:05 UTC
Last enriched: 06/24/2026, 22:02:58 UTC
Last updated: 06/25/2026, 03:27:38 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.