Visual Studio
Records
4
Disclosed CVEs
4
Exploited (sev 3–4)
0
CISA KEV flagged
0
Newest record 2026-02-10 · 4 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Patch now: confirmed exploitation or KEV · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for Visual Studio has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
▃ █
Nov ’244 disclosed · peak 3 in Feb ’26Oct ’26
Disclosed CVEs, no confirmed exploitation · 4
- 2026-02-10CVE-2026-21523CVE-2026-21523: Race condition in GitHub Copilot and Visual Studio2 Disclosedtoctou · rce
- 2026-02-10CVE-2026-21256CVE-2026-21256: RCE via Command Injection in GitHub Copilot and Visual Studio2 Disclosedgithub-copilot · rce
- 2026-02-10CVE-2026-21257CVE-2026-21257: Privilege Escalation via Command Injection in GitHub Copilot2 Disclosedgithub-copilot · privilege-escalation
- 2025-08-12CVE-2025-53773CVE-2025-53773: Command Injection Vulnerability in GitHub Copilot and Visual Studio2 Disclosedcommand-injection · github-copilot
This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.