CVE-2026-102869: Type Confusion Flaw in Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 Scores 8.8 on CVSS
A newly published high vulnerability in Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 carries a CVSS score of 8.8. Here is what is affected and how to respond.

Key points
- CVE-2026-102869 affects Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2.
- CVSS 8.8 (High).
- No exploitation confirmed yet.
A high type confusion tracked as CVE-2026-102869 has been published in the National Vulnerability Database for Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2, with a CVSS base score of 8.8.
At a glance
- CVE
- CVE-2026-102869
- Product
- Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2
- CVSS
- 8.8 High
- Weakness
- type confusion
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: Access of resource using incompatible type ('type confusion') in .NET and Visual Studio allows an unauthorized attacker to elevate privileges over a network.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 | before 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0 |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.7.2 | before 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.8 | before 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0 |
| Microsoft | Microsoft .NET Framework 3.5 AND 4.8.1 | before 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 |
| Microsoft | Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 | before 4.7.4150.0 |
| Microsoft | Microsoft .NET Framework 4.8 | before 4.8.4811.0 |
| Microsoft | Microsoft .NET Framework 4.8.1 | before 4.8.9363.0 |
| Microsoft | Microsoft Visual Studio 2022 version 17.14 | before 17.14.42 |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C.
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-102869
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-102869?
CVE-2026-102869 is a type confusion vulnerability in Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2.
How severe is CVE-2026-102869?
It has a CVSS score of 8.8 High.
Is CVE-2026-102869 being exploited?
There is no public confirmation of exploitation at the time of publication.


