Vulnerabilities

Vulnerability · CVE-2026-96222

Microsoft Security Advisory CVE-2026-96222 - .NET Spoofing Vulnerability

Published Oct 13, 2026 · catalog updated Oct 13, 2026 · Microsoft Security Advisory -

Check if you run it

No confirmed exploitation is on record for CVE-2026-96222. EPSS is 0.58%. Act only if a listed version of Microsoft Security Advisory - is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Microsoft Security Advisory -).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.58%
Remediation
Version ranges on file
Affected products
nuget System.Security.Cryptography.Xml

## Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in System.Security.Cryptography.Xml. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. can accept serialized certificate formats containing attacker-controlled chain metadata instead of requiring a plain X.509 certificate, contributing to certificate-forgery and token-spoofing paths. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/474 ## CVSS Details - **Version:** 3.1 - **Severity:** High - **Score:** 7.4 - **Vector:** - **Weakness:** CWE-295 (Improper Certificate Validation) ## Affected Platforms - **Platforms:** Windows, Linux, macOS - **Architectures:** All ## Affected Packages The vulnerability affects Microsoft .NET projects that use an affected package version listed below. Package name | Affected version | Patched version ------------ | ---------------- | --------------- [System.Security.Cryptography.Xml](https://www.nuget.org/packages/System.Security.Cryptography.Xml) | >= 8.0.0, How do I know if I am affected? If using a package listed in [affected packages](#affected-packages), you're exposed to the vulnerability. ### How do I fix the issue? 1. To fix the issue please install the latest version of .NET. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. 2. If your application references the vulnerable package, update the package reference to the patched version. You can list the versions you have installed by running the command. Once you have installed the updated runtime or SDK, restart your apps for the update to take effect. Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • nuget System.Security.Cryptography.Xml>= 8.0.0, <= 8.0.4

How to fix CVE-2026-96222

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-96222. EPSS is 0.58%. Act only if a listed version of Microsoft Security Advisory - is installed.

Which versions are affected?

Compare what you have installed with System.Security.Cryptography.Xml >= 8.0.0, <= 8.0.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-295: Improper Certificate Validation. EPSS 0.58%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 13, 2026 · GitHub Advisory Database

    Detected

    ## Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in System.Security.Cryptography.Xml. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. can accept serialized certificate formats containing attacker-controlled chain metadata instead of requiring a plain X.509 certif

  2. Oct 13, 2026 · GitHub Advisory Database

    Updated

    ## Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in System.Security.Cryptography.Xml. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. can accept serialized certificate formats containing attacker-controlled chain metadata instead of requiring a plain X.509 certif

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.