CVE-2025-21172 | .NET and Visual Studio Remote Code Execution Vulnerability

.NET and Visual Studio Remote Code Execution Vulnerability

Published: 2025-01-14 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-21172 is rated Moderate Risk (57.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.76%). EPSS rose +1.18% over the last day, indicating growing attacker interest. 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-21172

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.59% 1.76% +1.18%
2 2026-06-05 0.43% 0.59% +0.15%
3 2026-02-22 — 0.43% —

Full EPSS history (16 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
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.
 1.6 5.9 [email protected]

Weakness enumeration for CVE-2025-21172

GitHub Security Advisory for CVE-2025-21172

GHSA-jjcv-wr2g-4rv4 · Severity: high · Ecosystem: nuget — Microsoft Security Advisory CVE-2025-21172 | .NET and Visual Studio Remote Code Execution Vulnerability

OS Trackers for CVE-2025-21172

vendor priority summary link
alpine high CVE-2025-21172: 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-21172
redhat high — https://access.redhat.com/security/cve/CVE-2025-21172
ubuntu medium CVE-2025-21172 medium priority: Ubuntu including 4 source packages (dotnet6, dotnet7, dotnet8, dotnet9), 32 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 22, needs-triage 4, released 4, ignored 2. https://ubuntu.com/security/CVE-2025-21172

Affected software / configurations for CVE-2025-21172

Vendor Product Version Raw CPE
microsoft .net 8.0.0 cpe:2.3:a:microsoft:.net:8.0.0:*:*:*:*:*:*:*
microsoft .net 9.0.0 cpe:2.3:a:microsoft:.net:9.0.0:*:*:*:*:*:*:*
microsoft visual_studio_2017 >= 15.0, <= 15.8 cpe:2.3:a:microsoft:visual_studio_2017:*:*:*:*:*:*:*:*
microsoft visual_studio_2019 >= 16.0, <= 16.10 cpe:2.3:a:microsoft:visual_studio_2019:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.6.0, < 17.6.22 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.8.0, < 17.8.17 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.10.0, < 17.10.10 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.12.0, < 17.12.4 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*

References for CVE-2025-21172

cvelogic Threat Intelligence