Microsoft Corp Microsoft .NET Framework 4.6

Name: Microsoft Corp Microsoft .NET Framework 4.6
Brand: Microsoft Corp

productRU

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

by severity

5critical18high12medium0low

updated 2026-10-27

vulnerabilities (41)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2020-0646US	critical9.8OT critical	99.2% (100th)	KEV	no fix	2020-01-14	—
CVE-2024-29059US	—OT critical	98.6% (100th)	KEV	no fix	2024-03-23	—
CVE-2020-1147US	high7.8OT critical	94.0% (100th)	KEV	no fix	2020-07-14	—
CVE-2017-8759US	high7.8OT critical	88.7% (100th)	KEV	no fix	2017-09-13	—
CVE-2017-0160US	high7.8	17.8% (97th)	Exploit	no fix	2017-04-12	—
CVE-2019-1083US	high7.5	7.80% (95th)	Exploit	no fix	2019-07-15	—
CVE-2019-1006US	high7.5	6.07% (93rd)	Exploit	no fix	2019-07-15	—
CVE-2015-6096US	medium4.3	61.0% (99th)	—	no fix	2015-11-11	—
CVE-2015-6099US	medium4.3	47.6% (99th)	—	no fix	2015-11-11	—
CVE-2018-8421US	critical9.8	29.1% (98th)	—	no fix	2018-09-13	—
CVE-2016-3255US	high7.5	24.7% (98th)	—	no fix	2016-07-13	—
CVE-2015-2526US	medium5.0	23.9% (98th)	—	no fix	2015-09-09	—
CVE-2018-8540US	critical9.8	21.6% (98th)	—	no fix	2018-12-12	—
CVE-2016-0132US	critical9.8	21.5% (98th)	—	no fix	2016-03-09	—
CVE-2016-0047US	high7.5	20.1% (97th)	—	no fix	2016-02-10	—
CVE-2016-0033US	high7.5	17.6% (97th)	—	no fix	2016-02-10	—
CVE-2020-0606US	high8.8	17.2% (97th)	—	no fix	2020-01-14	—
CVE-2020-0605US	high8.8	17.1% (97th)	—	no fix	2020-01-14	—
CVE-2019-0613US	high8.8	15.4% (97th)	—	no fix	2019-03-05	—
CVE-2016-0148US	high7.8	13.9% (97th)	—	no fix	2016-04-12	—
CVE-2019-1113US	high8.8	10.00% (96th)	—	no fix	2019-07-15	—
CVE-2019-0545US	high7.5	9.61% (95th)	—	no fix	2019-01-08	—
CVE-2016-0149US	medium5.9	8.39% (95th)	—	no fix	2016-05-11	—
CVE-2023-36049US	critical9.8	6.79% (94th)	—	no fix	2023-11-14	—
CVE-2020-1108US	high7.5	6.46% (94th)	—	no fix	2020-05-21	—
CVE-2019-0981US	high7.5	4.94% (92nd)	—	no fix	2019-05-16	—
CVE-2019-0980US	high7.5	4.94% (92nd)	—	no fix	2019-05-16	—
CVE-2019-0657US	medium5.9	4.52% (91st)	—	no fix	2019-03-05	—
CVE-2021-24111US	medium5.0	3.84% (90th)	—	no fix	2021-02-25	—
CVE-2022-26832US	medium5.0	3.61% (89th)	—	no fix	2022-04-15	—
CVE-2020-16937US	medium4.3	3.29% (88th)	—	no fix	2020-10-16	—
CVE-2022-30130US	medium4.3	3.15% (88th)	—	no fix	2022-05-10	—
CVE-2024-43484US	—	2.96% (87th)	—	no fix	2024-10-08	—
CVE-2023-36560US	high8.8	2.91% (87th)	—	no fix	2023-11-14	—
CVE-2024-43483US	—	2.90% (87th)	—	no fix	2024-10-08	—
CVE-2025-21176US	—	2.38% (84th)	—	no fix	2025-01-14	—
CVE-2022-26929US	—	1.57% (75th)	—	no fix	2022-09-13	—
CVE-2019-0864US	medium5.5	1.35% (71st)	—	no fix	2019-05-16	—
CVE-2020-1476US	medium5.5	1.13% (66th)	—	no fix	2020-08-17	—
CVE-2019-1142US	medium5.5	1.04% (64th)	—	no fix	2019-09-11	—
CVE-2025-36855US	—	0.77% (55th)	—	no fix	2025-09-08	—

weaknesses (8)

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

CWE-20Improper Input Validation16 CVEs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor7 CVEs
CWE-19CWE-194 CVEs
CWE-94Improper Control of Generation of Code ('Code Injection')4 CVEs
CWE-264CWE-2643 CVEs
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer2 CVEs
CWE-126Buffer Over-read2 CVEs
CWE-407Inefficient Algorithmic Complexity2 CVEs

sources (1)

Which sources assert this record, and when.

RUBDU (FSTEC Data Security Threats Database)41 CVEs

scry

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

Free scan