CVE Tools

CVE-2026-108398

.NET Framework Security Feature Bypass Vulnerability

No known exploitation. No EPSS score yet. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2Affected: ≥ 3.0.0.0, < 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0Upgrade to: 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0Stated by: CVE record
  • Microsoft .NET Framework 3.5 AND 4.7.2Affected: ≥ 4.7.0, < 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0Upgrade to: 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0Stated by: CVE record
  • Microsoft .NET Framework 3.5 AND 4.8Affected: ≥ 4.8.0, < 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0Upgrade to: 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0Stated by: CVE record
  • Microsoft .NET Framework 3.5 AND 4.8.1Affected: ≥ 4.8.1, < 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0Upgrade to: 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0Stated by: CVE record
  • Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2Affected: ≥ 4.7.0, < 4.7.4150.0Upgrade to: 4.7.4150.0Stated by: CVE record

Versions as the sources state them. 2 more products have version data. Full version matrix after sign-in

Coverage timeline

2 publishers
  1. Vendor patch released

    ·Krebs on Security

Sourced from public security reporting — each date is when it was published, not when it happened. 3 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

Untrusted search path in .NET Framework allows an authorized attacker to bypass a security feature locally.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

No EPSS score yet. New CVEs are usually scored within a few days.

Lifecycle

5 events over 0 days, from the signal feeds we watch.

  1. Publishedweakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.