System.Security.Cryptography.Cose
Affected
- introduced
8.0.0, fixed8.0.2(ecosystem)
Fixed versions
8.0.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-dotnet-2026-21218, BIT-dotnet-sdk-2026-21218, CVE-2026-21218
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
<a name="executive-summary"></a>Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0, .NET 9.0, and .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
An attacker could exploit this vulnerability by crafting a malicious payload that bypasses the security checks in the affected System.Security.Cryptography.Cose versions, potentially leading to unauthorized access or data manipulation.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/380
<a name="mitigation-factors"></a>Mitigation factors
If your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component.
<a name="affected-packages"></a>Affected Packages
The vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below
<a name=".NET 10"></a>.NET 10
Package name | Affected version | Patched version
------------ | ---------------- | -------------------------
System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3
<a name=".NET 9"></a>.NET 9
Package name | Affected version | Patched version
------------ | ---------------- | -------------------------
System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13
<a name=".NET 8"></a>.NET 8
Package name | Affected version | Patched version
------------ | ---------------- | -------------------------
System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
If an affected package listed in [affected software](#affected-software) or [affected packages](#affected-packages), you're exposed to the vulnerability.
<a name="how-fix"></a>How do I fix the issue?
To update the Using the System.Security.Cryptography.Cose NuGet package, use one of the following methods:
NuGet Package Manager UI in Visual Studio:
Using the NuGet Package Manager Console in Visual Studio:
Update-Package -Id System.Security.Cryptography.Cose
Using the .NET CLI (Command Line Interface):
dotnet add package System.Security.Cryptography.Cose
Once you have updated the nuget package reference you must recompile and deploy your application. Additionally we recommend you update your runtime and/or SDKs, but it is not necessary to patch the vulnerability.
Other Information
Reporting Security Issues
If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
Acknowledgements
vcsjones with GitHub
Revisions
V1.0 (February 10, 2026): Advisory published.
High Basis: The source's own band: HIGH
8.0.0, fixed 8.0.2 (ecosystem)8.0.2
The export has no generic command for this ecosystem.
9.0.0, fixed 9.0.13 (ecosystem)9.0.13
The export has no generic command for this ecosystem.
10.0.0, fixed 10.0.3 (ecosystem)10.0.3
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0