Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-69306: Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a securi

45
This month
HIGH 8.2WATCHLISTUPGRADE

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

Not failing securely ('failing open') 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.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.5% (top 55%)
CISA exploited listNo
WeaknessCWE-636
Published2026-08-11
Last modified2026-10-23
Publisher (CNA): Microsoft Corporation · Vendor: microsoft

Am I affected?

Timeline

microsoft visual studio code UPGRADE
Affected: < 1.132.1
Fixed in: 1.132.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy visual-studio-code || rpm -q visual-studio-code || visual-studio-code --version
2. UPGRADE to 1.132.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.

Exact fixes by distribution

Fedora 46 · fooyin · FIXED · 0.14.1-6.fc46 · FEDORA-2026-a597ed324c · source
sudo dnf upgrade --advisory=FEDORA-2026-a597ed324c
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.

Related CVEs

References

← Back to latest CVEs