Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-57102: Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker

50
This month
HIGH 8.8WATCHLISTUPGRADE

CVE-2026-57102 is a high-severity flaw (CVSS 8.8) affecting visual studio code. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

Why this priority

  • High severity
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.8% (top 43%)
CISA exploited listNo
WeaknessCWE-200, CWE-829
Published2026-07-14
Last modified2026-10-24
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Share: LinkedIn · X · Reddit

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

microsoft visual studio code UPGRADE
Affected: >= 1.0.0 and < 1.128.1
Fixed in: 1.128.1
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy visual-studio-code || rpm -q visual-studio-code || visual-studio-code --version
2. UPGRADE to 1.128.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade visual-studio-code
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade visual-studio-code
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison visual-studio-code sudo apt install visual-studio-code=<VERSION_BEFORE_1.0.0> sudo apt-mark hold visual-studio-code
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list visual-studio-code sudo dnf downgrade visual-studio-code-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add visual-studio-code
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-57102?

visual studio code: upgrade to 1.128.1. Exact commands for each OS are on this page.

Is CVE-2026-57102 being exploited?

CVE-2026-57102 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-57102 affect?

CVE-2026-57102 affects visual studio code. Severity is high (CVSS 8.8). Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

How urgent is CVE-2026-57102?

Priority 50/100. High severity; On your watchlist

Software pages

Visual Studio vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.