cve.bz

CVE-2026-70165 microsoft: Link Following

6.7 mediumEPSS 0.4%

Medium (6.7) in microsoft. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Improper link resolution before file access ('link following') in .NET allows an authorized attacker to elevate privileges locally.

Severity

CVSS 3.1

6.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd 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-08. 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-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-70165 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-70165?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-70165?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-70165 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:.net 10.0 runtime
  • microsoft:.net 11.0 runtime
  • microsoft:.net 9.0 runtime
  • microsoft:microsoft visual studio 2022 version 17.14
  • microsoft:microsoft visual studio 2026 version 18.10

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft .NET 10.0 runtimefrom 10.0.0 before 10.0.402
Microsoft .NET 11.0 runtimefrom 11.0.0 before 11.0.100-rc.2
Microsoft .NET 9.0 runtimefrom 9.0.0 before 9.0.319, 9.0.122
Microsoft Visual Studio 2022 version 17.14from 17.14.0 before 17.14.42
Microsoft Visual Studio 2026 version 18.10from 18.10.0 before 18.10.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu22.04:LTSdotnet7no fix listedUBUNTU-CVE-2026-70165
Alpinev3.22, v3.23, v3.24dotnet9-runtime9.0.21-r0ALPINE-CVE-2026-70165
Alpinev3.23, v3.24dotnet10-runtime10.0.13-r0ALPINE-CVE-2026-70165

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires existing local system access and specific interaction or timing preconditions, precluding direct remote compromise. In standard Red Hat deployments, .NET applications run under dedicated unprivileged accounts or inside isolated container environments, which constrains the blast radius on the host. An attacker can only elevate privileges if they are able to redirect file operations carried out by an administrative or higher-privileged runtime process.

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-70165.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

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

References

Check your stackJSON