cve.bz

CVE-2026-114171 Visual Studio Code Security Feature Bypass Vulnerability

8.8 highEPSS 0.8%

High (8.8) in microsoft visual studio code. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
User interface (ui) misrepresentation of critical information in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.8% estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-451 User Interface (UI) Misrepresentation of Critical Information
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-114171 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114171?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114171?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114171 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-114171

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-114171](https://cve.bz/cve/badge/CVE-2026-114171.svg)](https://cve.bz/cve/CVE-2026-114171)

HTML:

<a href="https://cve.bz/cve/CVE-2026-114171"><img src="https://cve.bz/cve/badge/CVE-2026-114171.svg" alt="CVE-2026-114171"></a>

Affected

  • microsoft:visual studio code

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Visual Studio Codefrom 1.0.0 before 1.145.3

Attack patterns (CAPEC)

  • CAPEC-98 Phishing Likelihood: High · Severity: Very High
  • CAPEC-154 Resource Location Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-163 Spear Phishing Likelihood: High · Severity: High
  • CAPEC-164 Mobile Phishing Likelihood: High · Severity: High
  • CAPEC-173 Action Spoofing Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON