CVE-2026-32178 | .NET Spoofing Vulnerability

Improper neutralization of special elements in .NET allows an unauthorized attacker to perform spoofing over a network.

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

CVE-2026-32178 is rated Low Risk (36.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-2026-32178

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-22 0.05% 0.06% +0.01%
2 2026-04-17 0.05% 0.05% -0.00%
3 2026-04-15 — 0.05% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-32178

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:L/PR:N/UI:N/S:U/C:H/I:N/A:N 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:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-32178

GitHub Security Advisory for CVE-2026-32178

GHSA-vmwf-m9c5-3jvc · Severity: low · Ecosystem: nuget — Microsoft Security Advisory CVE-2026-32178 – .NET Spoofing Vulnerability

OS Trackers for CVE-2026-32178

vendor priority summary link
alpine — CVE-2026-32178: 3 source package rows (dotnet10-runtime, dotnet8-runtime, dotnet9-runtime); 6 state rows across 2 repos (3.23-community, edge-community); fixed 6, open 0. https://security.alpinelinux.org/vuln/CVE-2026-32178
redhat high — https://access.redhat.com/security/cve/CVE-2026-32178
suse high CVE-2026-32178 severity important: SUSE including 79 source package names (aspnetcore-runtime-10.0-10.0.6-1.el8_10, aspnetcore-runtime-8.0-8.0.26-1.el10_1, …), 79 product×package rows across 3 product lines (SUSE Liberty Linux 10, SUSE Liberty Linux 8, SUSE Liberty Linux 9): Fixed 79. https://www.suse.com/security/cve/CVE-2026-32178/
ubuntu medium CVE-2026-32178 medium priority: Ubuntu including 5 source packages (dotnet10, dotnet6, dotnet7, dotnet8, dotnet9), 45 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 31, released 10, needs-triage 2, deferred 1, ignored 1. https://ubuntu.com/security/CVE-2026-32178

Affected software / configurations for CVE-2026-32178

Vendor Product Version Raw CPE
microsoft .net >= 10.0.0, < 10.0.6 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft .net >= 8.0.0, < 8.0.26 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft .net >= 9.0.0, < 9.0.15 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.12.0, < 17.12.19 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.14.0, < 17.14.30 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*

References for CVE-2026-32178

cvelogic Threat Intelligence