CVE-2026-47284: Microsoft Visual Studio Code · Information Exposure
Affects Microsoft Visual Studio CodeSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.123.2 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.123.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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
Weaponized: 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 29 Oct 2026.
What to do
Upgrade Microsoft Visual Studio Code to 1.123.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MicrosoftVisual Studio Code | Affected
| Fixed in
|
AI-suggested
Microsoft has released an official fix for this vulnerability. Users and administrators should apply the vendor-provided update to Visual Studio Code to remediate this issue. Refer to the Microsoft advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47284 for detailed patch information and update instructions.
Description
Exposure of sensitive information to an unauthorized actor in Visual Studio Code allows an unauthorized attacker to disclose information over a network.