CVE-2025-26646 | .NET, Visual Studio, and Build Tools for Visual Studio Spoofing Vulnerability

External control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio allows an authorized attacker to perform spoofing over a network.

Published: 2025-05-13 Last update: 2025-07-10 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-26646 is rated Moderate Risk (54/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.06%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-26646

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.10% 1.06% +0.96%
2 2026-05-25 0.24% 0.10% -0.14%
3 2026-04-01 — 0.24% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-26646

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.0 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.1 5.9 [email protected]

Weakness enumeration for CVE-2025-26646

GitHub Security Advisory for CVE-2025-26646

GHSA-h4j7-5rxr-p4wc · Severity: high · Ecosystem: nuget — Microsoft.Build.Tasks.Core .NET Spoofing Vulnerability

OS Trackers for CVE-2025-26646

vendor priority summary link
alpine — CVE-2025-26646: 2 source package rows (dotnet8-runtime, dotnet9-runtime); 6 state rows across 3 repos (3.21-community, 3.22-community, edge-community); fixed 6, open 0. https://security.alpinelinux.org/vuln/CVE-2025-26646
redhat high — https://access.redhat.com/security/cve/CVE-2025-26646
ubuntu medium CVE-2025-26646 medium priority: Ubuntu including 4 source packages (dotnet6, dotnet7, dotnet8, dotnet9), 40 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 26, released 8, needs-triage 4, deferred 1, ignored 1. https://ubuntu.com/security/CVE-2025-26646

Affected software / configurations for CVE-2025-26646

Vendor Product Version Raw CPE
microsoft build_tools < 17.13.7 cpe:2.3:a:microsoft:build_tools:*:*:*:*:*:visual_studio:*:*
microsoft visual_studio_2022 >= 17.8.0, < 17.8.21 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.10.0, < 17.10.15 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.12.0, < 17.12.8 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.13.0, < 17.13.7 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft .net >= 9.0.0, < 9.0.5 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft .net >= 8.0.0, < 8.0.16 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*

References for CVE-2025-26646

cvelogic Threat Intelligence