CVE-2026-102869: .NET and Visual Studio Elevation of Privilege Vulnerability
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.83% (FIRST EPSS); higher than 58.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0; Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0; Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0.
Low priority for now. Upgrade to Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0; Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0; Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Access of resource using incompatible type ('type confusion') in .NET and Visual Studio allows an unauthorized attacker to elevate privileges over a network.
- Published
- Oct 13, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-843
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2
- 3.0.0.0 and later · before 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0affected
Microsoft Microsoft .NET Framework 3.5 AND 4.7.2
- 4.7.0 and later · before 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8
- 4.8.0 and later · before 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0affected
Microsoft Microsoft .NET Framework 3.5 AND 4.8.1
- 4.8.1 and later · before 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0affected
Microsoft Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2
- 4.7.0 and later · before 4.7.4150.0affected
Microsoft Microsoft .NET Framework 4.8
- 4.8.0 and later · before 4.8.4811.0affected
Microsoft Microsoft .NET Framework 4.8.1
- 4.8.0.0 and later · before 4.8.9363.0affected
Microsoft Microsoft Visual Studio 2022 version 17.14
- 17.14.0 and later · before 17.14.42affected
Microsoft Microsoft Visual Studio 2026 version 18.10
- 18.10.0 and later · before 18.10.4affected
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-108398.NET Framework Security Feature Bypass Vulnerability35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows 10 version 1607 | 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0 · KB5126868 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2016 | 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0 · KB5126868 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2019 | 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 · KB5127666 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 version 1809 | 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0 · KB5127666 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 1809 | 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0 · KB5127685 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 21H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.4811.0 · KB5127683 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 version 22H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.4811.0 · KB5127683 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 | 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0 · KB5127685 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.4811.0 · KB5127687 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 21H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 · KB5127689 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 10 version 22H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 · KB5127689 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 23H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 · KB5127692 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 24H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 · KB5127690 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 25H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 · KB5127690 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 26H2 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.10008.0 · KB5127694 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 · KB5127693 | Microsoft (MSRC) |
| Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2025 | 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0 · KB5127690 | Microsoft (MSRC) |
| Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 | 4.7.4150.0 · KB5127667 | Microsoft (MSRC) |
| Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2 on Windows Server 2012 R2 | 4.7.4150.0 · KB5127668 | Microsoft (MSRC) |
| Microsoft .NET Framework 4.8 on Windows 10 version 1607 | 4.8.4811.0 · KB5127684 | Microsoft (MSRC) |
| Microsoft .NET Framework 4.8 on Windows Server 2012 | 4.8.4811.0 · KB5127686 | Microsoft (MSRC) |
| Microsoft .NET Framework 4.8 on Windows Server 2012 R2 | 4.8.4811.0 · KB5127688 | Microsoft (MSRC) |
| Microsoft .NET Framework 4.8 on Windows Server 2016 | 4.8.4811.0 · KB5127684 | Microsoft (MSRC) |
| Microsoft .NET Framework 4.8.1 on Windows 11 version 26H1 | 4.8.9363.0 · KB5127691 | Microsoft (MSRC) |
| Microsoft Visual Studio 2022 version 17.14 | 17.14.42 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2026 version 18.10 | 18.10.4 · Release Notes | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 12, 2026+30 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.