CVE-2026-69154: Coder VS Code extension allowed workspace settings to trigger command execution
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.14.6
Event History
Frequently Asked Questions
Which users are exposed to this issue?
Users running Coder VS Code extension versions from 0.1.20 through versions before 1.14.6 are exposed if they open a malicious repository or workspace. The extension can consume the malicious workspace settings even when the workspace is untrusted.
What must an attacker do to exploit the vulnerability?
An attacker must provide a repository or workspace containing attacker-controlled .vscode/settings.json values for affected Coder settings, then persuade a victim with the extension installed to open it. On extension activation, settings including coder.headerCommand or coder.tlsCertRefreshCommand can be executed as shell commands with the victim user's privileges.
Does VS Code untrusted-workspace mode prevent exploitation?
No. The extension declares support for untrusted workspaces but does not prevent use of the workspace-controlled security-sensitive settings in that mode.
What should teams do to remediate this issue?
Update the Coder VS Code extension to version 1.14.6. Until updating, avoid opening untrusted repositories or workspaces with the extension installed, particularly those containing .vscode/settings.json.