CVE-2026-69154 · Package
NO FIX YET · SEE WHAT TO DO
From version 0.1.20 until 1.14.6, the Coder VS Code extension reads security-sensitive settings from a repository's .vscode/settings.json. An attacker who supplies a malicious repository can get shell commands run with the victim's privileges when the victim opens it with the extension installed.
first public Jul 6, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams whose developers use the Coder VS Code extension to open Coder workspaces from versions 0.1.20 through 1.14.6. Exposure comes from opening a repository whose .vscode/settings.json sets Coder security-sensitive options, including when the workspace is untrusted. Teams not using the extension can skip it.
Not affected if extension-not-installed, version-1.14.6-or-later
Who cares coder, developer-tools, vs-code
code --list-extensions --show-versions, and look for coder.coder-remote at a version from 0.1.20 up to 1.14.6..vscode/settings.json in repositories opened with the extension for coder.headerCommand, coder.tlsCertRefreshCommand and other coder.* settings.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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
1.14.6.NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.