CVE-20XX-?
agent?

Microsoft Visual Studio Code CVEs.

Published CVEs affecting Microsoft Visual Studio Code, ranked by exploit odds.

7 CVEs · updated 2026-11-18 22:26 UTC

Reset all
  1. CVE-2026-121663

    Incomplete list of disallowed inputs in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

    Other Microsoft Visual Studio Code

    8.8 HIGH 1.0% exploit odds Fix listed
  2. CVE-2026-114171

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

    Other Microsoft Visual Studio Code

    8.8 HIGH 0.8% exploit odds Fix listed
  3. CVE-2026-119976

    External control of file name or path in Visual Studio Code - GitHub Pull Requests and Issues Extension allows an unauthorized attacker to disclose information over a network.

    Other Microsoft Visual Studio Code

    6.5 MEDIUM 0.7% exploit odds Fix listed
  4. CVE-2026-121660

    Incomplete list of disallowed inputs in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

    Other Microsoft Visual Studio Code

    7.5 HIGH 0.7% exploit odds Fix listed
  5. CVE-2026-121661

    Incomplete list of disallowed inputs in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.

    Other Microsoft Visual Studio Code

    7.8 HIGH 0.5% exploit odds Fix listed
  6. CVE-2026-121665

    Trust boundary violation in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

    Other Microsoft Visual Studio Code

    8.8 HIGH 0.4% exploit odds Fix listed
  7. CVE-2026-102236

    Improper restriction of rendered ui layers or frames in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.

    Other Microsoft Visual Studio Code

    8.6 HIGH 0.4% exploit odds Fix listed

All CVEs affecting Microsoft Visual Studio Code that appear in CVE.org and NVD, sorted by how likely they are to be exploited (EPSS), with fix status and timeline.