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

Untrusted search path in .NET and Visual Studio allows an unauthorized attacker to execute code over a network.

Published: 2025-06-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-30399 is rated Moderate Risk (48/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.28%). 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-30399

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-05-13 0.24% 0.28% +0.04%
2 2026-05-02 0.25% 0.24% -0.01%
3 2026-04-09 — 0.25% —

Full EPSS history (10 records total)

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

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-30399

GitHub Security Advisory for CVE-2025-30399

GHSA-266m-wp2v-x7mq · Severity: high · Ecosystem: nuget — Microsoft Security Advisory CVE-2025-30399 | .NET Remote Code Vulnerability

OS Trackers for CVE-2025-30399

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

Affected software / configurations for CVE-2025-30399

Vendor Product Version Raw CPE
microsoft visual_studio_2022 >= 17.8.0, < 17.8.22 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.10.0, < 17.10.16 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.12.0, < 17.12.9 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.14.0, < 17.14.5 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft .net >= 9.0.0, < 9.0.6 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft .net >= 8.0.0, < 8.0.17 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft powershell >= 7.4, < 7.4.11 cpe:2.3:a:microsoft:powershell:*:*:*:*:*:*:*:*
microsoft powershell >= 7.5, < 7.5.2 cpe:2.3:a:microsoft:powershell:*:*:*:*:*:*:*:*

References for CVE-2025-30399

cvelogic Threat Intelligence