Microsoft Visual Studio 2019 16.0-16.11

productDE

cpe:/a:microsoft:visual_studio_2019:16.0_-_16.11

A product tracked in the threat graph; the vulnerabilities below are known to affect it.

KEV-listed

public exploit

EPSS ≥ 10%

by severity

1critical0high0medium0low

updated 2026-10-27

vulnerabilities (17)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2024-50338US	—	3.17% (88th)	—	no fix	2025-01-14	—
CVE-2025-21176US	—	2.38% (84th)	—	no fix	2025-01-14	—
CVE-2025-21172US	—	1.84% (79th)	—	no fix	2025-01-14	—
CVE-2025-29813US	critical9.8	1.77% (78th)	—	no fix	2025-05-08	—
CVE-2025-21171US	—	1.72% (77th)	—	no fix	2025-01-14	—
CVE-2025-21178US	—	1.60% (76th)	—	no fix	2025-01-14	—
CVE-2025-21173US	—	1.30% (70th)	—	no fix	2025-01-14	—
CVE-2025-26646US	—	1.27% (70th)	—	no fix	2025-05-13	—
CVE-2025-24070US	—	1.01% (63rd)	—	no fix	2025-03-11	—
CVE-2025-24043US	—	0.91% (60th)	—	no fix	2025-03-11	—
CVE-2025-21264US	—	0.79% (56th)	—	no fix	2025-05-13	—
CVE-2025-32702US	—	0.62% (50th)	—	no fix	2025-05-13	—
CVE-2025-26631US	—	0.57% (47th)	—	no fix	2025-03-11	—
CVE-2025-21405US	—	0.55% (46th)	—	no fix	2025-01-14	—
CVE-2025-32703US	—	0.50% (43rd)	—	no fix	2025-05-13	—
CVE-2025-25003US	—	0.46% (39th)	—	no fix	2025-03-11	—
CVE-2025-24998US	—	0.46% (39th)	—	no fix	2025-03-11	—

The flaw types (CWEs) most of these CVEs share.

Which sources assert this record, and when.

scry

Products carry known vulnerabilities once they are exposed to the internet. See what is exposed on your perimeter with a free passive scan.