dbcve.org
Visual Studio CodeApplication · Microsoft

CVE-2026-41610

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 1.119.1 or later.
See remediation →
53/100
Remediation priority · Moderate
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
Improper neutralization of input during web page generation ('cross-site scripting') in Visual Studio Code allows an unauthorized attacker to bypass a security feature 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

Cross-site scripting (XSS) vulnerability in Visual Studio Code where improper input neutralization during web page generation allows an unauthorized attacker to bypass a security feature locally. The vulnerability stems from insufficient sanitization of user-supplied input in web views or the embedded browser component of VS Code.

MitigationApply vendor patches or update to the patched version of Visual Studio Code once available. Review and harden VS Code settings related to content security and webview configurations as a defensive measure.

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.119.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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Determine installed VS Code version
    Run 'code --version' in terminal, or open VS Code and go to Help > About to view the version number
    Affected if The version shown is less than 1.119.1 (for example, 1.119.0, 1.118.x, or earlier)
  2. Check for VS Code Insiders variant
    Run 'code-insiders --version' to see if the Insiders build is installed; also check via Help > About in that variant
    Affected if The Insiders version is less than 1.119.1
  3. Identify webview-based extensions
    Open VS Code Extensions view (Ctrl+Shift+X) and review installed extensions. Look for extensions that use web views (check extension description or run 'code --list-extensions' in terminal)
    Affected if Extensions using webview functionality are installed and the VS Code version is below 1.119.1
  4. Review webview security settings
    Open Settings (Ctrl+,) and search for 'webview' to review webview-related configuration options that control security behavior
    Affected if Non-default webview settings are configured and the VS Code version is below 1.119.1

You are affected if your installed Visual Studio Code version (including Insiders) is less than 1.119.1 and you use extensions that leverage web views, as the XSS vulnerability exists in the web view generation process.

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.119.1 or later
Fixed in 1.119.1
Interim mitigation

Apply vendor patches or update to the patched version of Visual Studio Code once available. Review and harden VS Code settings related to content security and webview configurations as a defensive measure.

Recommended fix Moderate confidence

Visual Studio Code 1.119.1 or later

  1. 1. Open Visual Studio Code
  2. 2. Go to Help > Check for Updates (or use the Command Palette and search for 'Check for Updates')
  3. 3. If an update is available, click 'Download and Install' to update to version 1.119.1 or later
  4. 4. Alternatively, download the latest version from the official Visual Studio Code website: https://code.visualstudio.com/
  5. 5. Restart Visual Studio Code after the update completes
  6. 6. Verify the version by going to Help > About and confirm the version number is 1.119.1 or higher

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

Fix this in Visual Studio Code Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41610 — 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-41610 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