Read the docs

Workspace settings enable command execution in Coder VS Code extension

Priority MEDIUM 49CWE-15Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-78.

Summary

The Coder VS Code extension (vscode-coder) from 0.1.20 before 1.14.6 lets a malicious repository set security-sensitive Coder settings through .vscode/settings.json, because workspace and folder scope overrides are permitted. Values such as coder.headerCommand and coder.tlsCertRefreshCommand are later run as shell commands (CWE-78), and other settings can redirect the CLI binary, inject flags, or disable TLS verification. A local user must open the malicious workspace or repository while the extension is installed, and commands then run with the victim's privileges. The flaw also affects untrusted workspaces because the extension does not block these settings there.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Fix Fixed vscode-coder (coder): 1.14.6

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
codervscode-coder0.1.20 to before 1.14.61.14.6Patch availableCNA
  • vscode-coder Vendorcoder Affected 0.1.20 to before 1.14.6 Fixed in 1.14.6 Patch available CNA

Remediation

Update the Coder VS Code extension (vscode-coder) to version 1.14.6 or later, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA vscode-coder (coder) Fixed in 1.14.6

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-69154

References

  • TI-2025-29799 code-server session cookie can be extracted by having user visit specially crafted proxy URL CVSS 3.1HIGH 8.3
  • TI-2025-37344 AgentAPI exposed user chat history via a DNS rebinding attack CVSS 3.1MEDIUM 6.5
  • TI-2026-34071 Coder: PKCS#7 signature bypass in Azure instance identity allows unauthenticated agent token theft CVSS 3.1CRITICAL 9.1
  • TI-2026-32394 Coder vulnerable to workspace auto-creation via crafted URL parameters without user consent CVSS 3.1HIGH 8.8
  • TI-2026-27585 Code Extension Marketplace has a Zip Slip Path Traversal CVSS 4.0HIGH 8.7
  • TI-2024-18523 Coder's OIDC authentication allows email with partially matching domain to register CVSS 3.1HIGH 8.2
See all 47 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences