cve.bz

CVE-2026-108398 microsoft: Untrusted Search Path

8.8 highEPSS 0.8%

High (8.8) in microsoft. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 57th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-426 Untrusted Search Path
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-108398 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-108398?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-108398?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-108398 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • microsoft:microsoft .net framework 3.5 and 4.6.2/4.7/4.7.1/4.7.2
  • microsoft:microsoft .net framework 3.5 and 4.7.2
  • microsoft:microsoft .net framework 3.5 and 4.8
  • microsoft:microsoft .net framework 3.5 and 4.8.1
  • microsoft:microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2
  • microsoft:microsoft .net framework 4.8
  • microsoft:microsoft .net framework 4.8.1

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft .NET Framework 3.5 AND 4.6.2/4.7/4.7.1/4.7.2from 3.0.0.0 before 2.0.50727.8987 AND 3.0.30729.8982 AND 4.7.4150.0
Microsoft .NET Framework 3.5 AND 4.7.2from 4.7.0 before 2.0.50727.9073 AND 3.0.30729.9070 AND 4.7.4150.0
Microsoft .NET Framework 3.5 AND 4.8from 4.8.0 before 2.0.50727.9073 AND 3.0.30729.9070 AND 4.8.4811.0
Microsoft .NET Framework 3.5 AND 4.8.1from 4.8.1 before 2.0.50727.9188 AND 3.0.30729.9171 AND 4.8.9363.0
Microsoft .NET Framework 4.6.2/4.7/4.7.1/4.7.2from 4.7.0 before 4.7.4150.0
Microsoft .NET Framework 4.8from 4.8.0 before 4.8.4811.0
Microsoft .NET Framework 4.8.1from 4.8.0.0 before 4.8.9363.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

An untrusted search path vulnerability was found in Microsoft .NET Framework. An authenticated local attacker could exploit this flaw by placing a specially crafted binary or dependency into an application search path. When an application loads the untrusted component, the attacker bypasses local security enforcement (such as application control policies), enabling arbitrary code execution and potential privilege escalation within the local operating system context.

Red Hat's mitigation

Enforce strict file system access controls and directory write permissions to prevent unprivileged users from writing files to application directories or search paths.

ProductPackageStateAdvisory
Red Hat Hardened Imagesdotnet8.0Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-108398.

Attack patterns (CAPEC)

  • CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON