Answer in brief
CVE-2026-69154 records a High severity (CVSS 7.8) vulnerability in Coder VS Code extension allowed workspace settings to trigger command execution. The current sources do not mark it as known exploited. The current feed maps coder/vscode-coder (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps coder/vscode-coder (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| coder/vscode-codergeneric | >=0.1.20 <1.14.6 | 1.14.6 |
Published upstream
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.