Visual Studio Code Security Feature Bypass Vulnerability
Affects Microsoft Security Response Center Visual Studio CodeSource GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 1.123.2 soon.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.123.2
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 9 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Microsoft Security Response Center Visual Studio Code to 1.123.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MicrosoftVisual Studio Code | Affected
| Fixed in
|
Description
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle
References
- msrc.microsoft.com/update-guide/vulnerability/CVE-2026-48569 (opens in a new tab)
- msrc.microsoft.com/csaf/advisories/2026/msrc_cve-2026-48569.json (opens in a new tab)
- microsoft.com/en-us/msrc/exploitability-index?rtc=1 (opens in a new tab)
- support.microsoft.com/lifecycle (opens in a new tab)
- first.org/cvss (opens in a new tab)