Visual Studio
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)
Exploited or KEV-listed · 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
Disclosed CVEs, no confirmed exploitation · 4
- closed8.0GitHub Copilot CVE-2026-21523: Race condition in GitHub Copilot and Visual Studio
Disclosed · since 10 Feb 2026 · CVE-2026-21523
AI - closed8.8GitHub Copilot CVE-2026-21256: RCE via Command Injection in GitHub Copilot and Visual Studio
Disclosed · since 10 Feb 2026 · CVE-2026-21256
AI - closed8.0GitHub Copilot CVE-2026-21257: Privilege Escalation via Command Injection in GitHub Copilot
Disclosed · since 10 Feb 2026 · CVE-2026-21257
AI - closed7.8GitHub Copilot CVE-2025-53773: Command Injection Vulnerability in GitHub Copilot and Visual Studio
Disclosed · since 12 Aug 2025 · CVE-2025-53773
AI
Fix status and fixed versions are recorded when a source states them (each record’s page shows what is known); check the vendor’s own advisory before acting.