Visual Studio is widely used enterprise developer software; a remote RCE on developer workstations risks codebase compromise and supply-chain impact, warranting broad IT notice.
CVE-2026-71328
Heap overflow in Visual Studio enabling remote code execution.
Is CVE-2026-71328 being exploited?
Not confirmed. CVE-2026-71328 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-71328?
CVE-2026-71328 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71328?
Yes. A fix has been recorded for CVE-2026-71328. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71328 affect?
CVE-2026-71328 affects Microsoft Visual Studio (IDE), Windows developer workstations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71328?
Apply Microsoft's security update immediately and restrict network access to developer workstations.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via heap-based buffer overflow; attacker can run arbitrary code, compromise developer machines, and access/source tamper.
Immediate action required
- affected>= 17.14.0 and < 17.14.40
- affected>= 18.9.0 and < 18.9.3
- affected>= 10.0.0 and < 10.0.12
- affected>= 11.0.0 and < 11.0 RC1
- affected>= 8.0.0 and < 8.0.31
- affected>= 9.0.0 and < 9.0.20
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.