CVE-2026-21218: Microsoft .NET 10.0 · Improper Handling of Missing Special Element
Affects Microsoft .NET 10.0Source CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 10.0.3 soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.0.3, 8.0.24, 9.0.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade .NET to 10.0.3 (10.0) or 8.0.24 (8.0) or 9.0.13 (9.0).
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft.NET 10.0 | Affected
| Fixed in
|
| Microsoft.NET 8.0 | Affected
| Fixed in
|
| Microsoft.NET 9.0 | Affected
| Fixed in
|
AI-suggested
Microsoft has released an official fix for this vulnerability. Users and administrators should apply the security update provided by Microsoft as detailed in their advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21218 to remediate this issue.
Description
Improper handling of missing special element in .NET allows an unauthorized attacker to perform spoofing over a network.