Skip to content
statance
MenuClose
high · CVSS 8.8

CVE-2026-102869

.NET and Visual Studio Elevation of Privilege Vulnerability

Published 13 Oct 2026 · Source updated 31 Oct 2026 · Retrieved 2026-10-31 21:59 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

See the source record for the publisher’s description.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2Microsoftaffected: 3.0.0.0 to < 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0See vendor advisory
Microsoft .NET Framework 3.5 AND 4.7.2Microsoftaffected: 4.7.0 to < 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0See vendor advisory
Microsoft .NET Framework 3.5 AND 4.8Microsoftaffected: 4.8.0 to < 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0See vendor advisory
Microsoft .NET Framework 3.5 AND 4.8.1Microsoftaffected: 4.8.1 to < 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0See vendor advisory
Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2Microsoftaffected: 4.7.0 to < 4.7.4150.0See vendor advisory
Microsoft .NET Framework 4.8Microsoftaffected: 4.8.0 to < 4.8.4811.0See vendor advisory
Microsoft .NET Framework 4.8.1Microsoftaffected: 4.8.0.0 to < 4.8.9363.0See vendor advisory
Microsoft Visual Studio 2022 version 17.14Microsoftaffected: 17.14.0 to < 17.14.42See vendor advisory
Microsoft Visual Studio 2026 version 18.10Microsoftaffected: 18.10.0 to < 18.10.4See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-01 01:55 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed