dbcve.org
Visual Studio CodeApplication · Microsoft

CVE-2026-47292

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 1.123.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Visual Studio Code contains a vulnerability where functionality from an untrusted control sphere is included, allowing an unauthorized local attacker to elevate privileges. This is a local privilege escalation vulnerability (CWE-494) where the VS Code process loads or executes untrusted code/modules, enabling the attacker to gain higher-level system access.

MitigationApply the vendor patch for Visual Studio Code as soon as it becomes available; until then, restrict user access to VS Code installations and monitor for suspicious extensions or modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Visual Studio CodeApplication
Affected:>= 1.0.0, < 1.123.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Visual Studio Code version
    Open VS Code and go to Help > About, or run 'code --version' from command line. Compare the version number to the affected range (>= 1.0.0 and < 1.123.1).
    Affected if The installed version is 1.0.0 through 1.123.0 (any version >= 1.0.0 but lower than 1.123.1)
  2. Review installed extensions from untrusted sources
    Open VS Code Extensions view (Ctrl+Shift+X) and list all installed extensions. Check for any extensions installed from unknown publishers, unofficial marketplaces, or untrusted developer accounts.
    Affected if One or more extensions are installed from untrusted or unknown sources
  3. Inspect user and workspace settings for untrusted configurations
    Open Settings editor (File > Preferences > Settings) and review settings.json files at both user and workspace levels. Look for settings that reference external URLs, custom scripts, or paths outside trusted directories.
    Affected if Settings contain references to untrusted external sources, scripts, or paths
  4. Check for custom tasks or extensions loading remote code
    Review .vscode/tasks.json files in projects and any custom task configurations. Check if any tasks or extensions execute scripts fetched from untrusted network locations.
    Affected if Tasks or extensions are configured to fetch or execute code from untrusted network sources

A user is affected if their VS Code version is between 1.0.0 and 1.123.0 AND they have extensions, settings, or configurations loaded from untrusted or unknown sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.123.1 or later
Fixed in 1.123.1
Interim mitigation

Apply the vendor patch for Visual Studio Code as soon as it becomes available; until then, restrict user access to VS Code installations and monitor for suspicious extensions or modifications.

Recommended fix High confidence

Visual Studio Code 1.123.1 or later

  1. Upgrade Visual Studio Code to version 1.123.1 or later
  2. On Windows: Use the installer from https://code.visualstudio.com/ or check for updates via Help > Check for Updates
  3. On macOS: Use the installer or check for updates via Code > Check for Updates
  4. On Linux: Use the package manager or snap to update to the latest version
Caveat Review extension compatibility before upgrading, as some extensions may not be compatible with newer VS Code versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Visual Studio Code Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47292 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data