CVE-2026-69154
7.8HighPublished 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User action
- Required
- Impact
- Full C/I/A compromise
- Weakness
- CWE-15, CWE-78
What an attacker gets
Attackers can execute arbitrary shell commands with the victim's privileges. This happens when a user opens a malicious repository or workspace containing a crafted .vscode/settings.json file.
Root cause
The extension incorrectly allows workspace-level configuration files to override security-sensitive settings, which are then executed as shell commands.
Affected versions
Coder VS Code extension versions 0.1.20 through 1.14.5.
CVSS v3.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Fix & remediation
Update the Coder extension to version 1.14.6 or later. Until updated, avoid opening untrusted repositories or workspaces in VS Code.
$ code --install-extension coder.coder-remote@1.14.6AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
The Coder VS Code extension opens Coder workspaces in VS Code with a single click. From 0.1.20 until 1.14.6, a malicious repository can provide .vscode/settings.json values for security-sensitive Coder settings because the extension permits workspace and folder scope to override those settings. Values such as coder.headerCommand and coder.tlsCertRefreshCommand are later executed as shell commands, while other affected settings can redirect the Coder CLI binary or download source, inject CLI or SSH flags, replace TLS material, disable TLS verification, or change identity and credential-storage behavior. A victim with the extension installed must open the malicious workspace or repository; when the extension activates, attacker-controlled commands can run with the victim user's privileges. The issue also affects untrusted workspaces because the extension declares untrusted-workspace support without preventing consumption of the workspace-controlled settings. This issue is fixed in version 1.14.6.