Skip to main content
Menu
CVEs

CVE

vscode-coder remote code execution via workspace settings

Affects Coder VS Code extension versions 0.1.20 up to but not including 1.14.6, when the extension is installed and a malicious workspace or repository is opened. No vendor rating is given; CVSS scores it High at 7.8. Fixed in 1.14.6.

CVE-2026-69154EUVD-2026-126673

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

7.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.14.6
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Coder VS Code extension versions 0.1.20 up to but not including 1.14.6 Victim has the Coder extension installed and opens a malicious workspace or repository

Published
Last modified
Reference
Last checked
13/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

The Coder VS Code extension reads security-sensitive settings from a malicious repository's workspace, so commands such as coder.headerCommand can run as shell commands with the victim's user privileges when the extension activates. A local attacker needs no login, but the victim must open the malicious workspace or repository, and the flaw also affects untrusted workspaces.

Original 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.

Who should check

Teams and developers running the Coder VS Code extension (coder.coder-remote) from 0.1.20 before 1.14.6, especially those opening untrusted repositories or workspaces.

“Coder VS Code extension versions greater than or equal to 0.1.20 and earlier than 1.14.6 are affected.”

github.com

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.8/10CVSS 7.8
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Coder VS Code extension versions 0.1.20 up to but not including 1.14.6 Victim has the Coder extension installed and opens a malicious workspace or repository
  • Upgrade to a fixed version: 1.14.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-69154 (Coder VS Code extension allowed workspace settings to trigger command execution), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-69154 (entry last updated 2026-11-16):
Affected:
- coder vscode-coder: from 0.1.20, fixed in 1.14.6
Fixed versions: 1.14.6.
Conditions (all must be true for the bug to be hit):
- Coder VS Code extension versions 0.1.20 up to but not including 1.14.6 (source: https://github.com/coder/vscode-coder/security/advisories/GHSA-9q2g-22gh-hmgg)
- Victim has the Coder extension installed and opens a malicious workspace or repository (source: https://github.com/coder/vscode-coder/security/advisories/GHSA-9q2g-22gh-hmgg)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-69154 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69154 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/coder/vscode-coder/security/advisories/GHSA-9q2g-22gh-hmgg
- https://github.com/coder/vscode-coder/pull/965
- https://github.com/coder/vscode-coder/commit/9ee5140aec532b347b72834767ea4f99c01666a0
- https://github.com/coder/vscode-coder/releases/tag/v1.14.6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-69154
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69154"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • coder vscode-coder

    From 0.1.20 · fixed in 1.14.6

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-69154

Is CVE-2026-69154 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Workspace settings in the Coder VS Code extension could trigger command execution. Attacker-controlled shell commands may run with the victim user's privileges. Other affected settings can redirect the CLI binary, inject flags, replace TLS material, disable TLS verification, or change identity and credential storage.Source: github.com

Which versions are affected by CVE-2026-69154?

vscode-coder: from 0.1.20 before 1.14.6.Source: cve.now feed data

Am I affected, and how do I check?

Coder VS Code extension versions 0.1.20 up to but not including 1.14.6 are affected. The setup involves the Coder extension being installed and a malicious workspace or repository being opened. The installed extension version can be checked in the VS Code Extensions view.Source: github.com

How do I fix CVE-2026-69154?

Upgrade the Coder VS Code extension to version 1.14.6 or later.Source: github.com