System.Security.Cryptography.Cose
Provides support for CBOR Object Signing and Encryption (COSE).
Activity
- Latest release
- 6d ago
- Total releases
- 81
- Cadence
- ~4 days
- Last 12 months
- 34
Details
- License
- MIT
- First release
- Mar 14, 2022
| Version | Released | |
|---|---|---|
9.0.20
patch
|
9.0.20
patch
Dependencies (1)
|
|
10.0.12
patch
|
10.0.12
patch
Dependencies (3)
|
|
11.0.0-rc.1.26425.128
pre
|
11.0.0-rc.1.26425.128
pre
Dependencies (3)
|
|
10.0.11
patch
|
10.0.11
patch
Dependencies (3)
|
|
9.0.19
patch
|
9.0.19
patch
Dependencies (1)
|
|
11.0.0-preview.7.26381.103
pre
|
11.0.0-preview.7.26381.103
pre
Dependencies (3)
|
|
10.0.10
patch
|
10.0.10
patch
Dependencies (3)
|
|
9.0.18
patch
|
9.0.18
patch
Dependencies (1)
|
|
11.0.0-preview.6.26359.118
pre
|
11.0.0-preview.6.26359.118
pre
Dependencies (3)
|
|
10.0.9
patch
|
10.0.9
patch
Dependencies (3)
|
|
9.0.17
patch
|
9.0.17
patch
Dependencies (1)
|
|
11.0.0-preview.5.26302.115
pre
|
11.0.0-preview.5.26302.115
pre
Dependencies (3)
|
|
10.0.8
patch
|
10.0.8
patch
Dependencies (3)
|
|
9.0.16
patch
|
9.0.16
patch
Dependencies (1)
|
|
11.0.0-preview.4.26230.115
pre
|
11.0.0-preview.4.26230.115
pre
Dependencies (3)
|
|
10.0.7
patch
|
10.0.7
patch
Dependencies (3)
|
|
9.0.15
patch
|
9.0.15
patch
Dependencies (1)
|
|
10.0.6
patch
|
10.0.6
patch
Dependencies (3)
|
|
11.0.0-preview.3.26207.106
pre
|
11.0.0-preview.3.26207.106
pre
Dependencies (3)
|
|
10.0.5
patch
|
10.0.5
patch
Dependencies (3)
|
|
11.0.0-preview.2.26159.112
pre
|
11.0.0-preview.2.26159.112
pre
Dependencies (3)
|
|
9.0.14
patch
|
9.0.14
patch
Dependencies (1)
|
|
10.0.4
patch
|
10.0.4
patch
Dependencies (3)
|
|
11.0.0-preview.1.26104.118
pre
|
11.0.0-preview.1.26104.118
pre
Dependencies (3)
|
|
9.0.13
patch
|
9.0.13
patch
Dependencies (1)
|
|
10.0.3
patch
|
10.0.3
patch
Dependencies (3)
|
|
8.0.2
patch
|
8.0.2
patch
Dependencies (1)
|
|
10.0.2
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
10.0.2
patch
Dependencies (3)
|
|
9.0.12
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.12
patch
Dependencies (1)
|
|
10.0.1
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
10.0.1
patch
Dependencies (3)
|
|
10.0.0
major
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
10.0.0
major
Dependencies (3)
|
|
9.0.11
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.11
patch
Dependencies (1)
|
|
10.0.0-rc.2.25502.107
pre
|
10.0.0-rc.2.25502.107
pre
Dependencies (3)
|
|
9.0.10
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.10
patch
Dependencies (1)
|
|
9.0.9
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.9
patch
Dependencies (1)
|
|
10.0.0-rc.1.25451.107
pre
|
10.0.0-rc.1.25451.107
pre
Dependencies (3)
|
|
10.0.0-preview.7.25380.108
pre
|
10.0.0-preview.7.25380.108
pre
Dependencies (3)
|
|
9.0.8
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.8
patch
Dependencies (1)
|
|
10.0.0-preview.6.25358.103
pre
|
10.0.0-preview.6.25358.103
pre
Dependencies (3)
|
|
9.0.7
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.7
patch
Dependencies (1)
|
|
9.0.6
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.6
patch
Dependencies (1)
|
|
10.0.0-preview.5.25277.114
pre
|
10.0.0-preview.5.25277.114
pre
Dependencies (2)
|
|
9.0.5
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.5
patch
Dependencies (1)
|
|
10.0.0-preview.4.25258.110
pre
|
10.0.0-preview.4.25258.110
pre
Dependencies (2)
|
|
10.0.0-preview.3.25171.5
pre
|
10.0.0-preview.3.25171.5
pre
Dependencies (2)
|
|
9.0.4
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.4
patch
Dependencies (1)
|
|
10.0.0-preview.2.25163.2
pre
|
10.0.0-preview.2.25163.2
pre
Dependencies (2)
|
|
9.0.3
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.3
patch
Dependencies (1)
|
|
10.0.0-preview.1.25080.5
pre
|
10.0.0-preview.1.25080.5
pre
Dependencies (2)
|
|
9.0.2
patch
1 CVE
CVE-2026-21218
GHSA-qvhc-9v3j-5rfw
BIT-dotnet-2026-21218
BIT-dotnet-sdk-2026-21218
Feb 10, 2026
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass Vulnerability
High
Network
Low
None
None
Microsoft Security Advisory CVE-2026-21218 | .NET Security Feature Bypass VulnerabilityExecutive summaryMicrosoft 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. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/380 Mitigation factorsIf your application does not use System.Security.Cryptography.Cose it is not affected. By default, no .NET applications reference this component. Affected PackagesThe vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below .NET 10Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 10.0.0, <= 10.0.2 | 10.0.3 .NET 9Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 9.0.0, <= 9.0.12 | 9.0.13 .NET 8Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Security.Cryptography.Cose | >= 8.0.0, <= 8.0.1 | 8.0.2 Advisory FAQHow do I know if I am affected?If an affected package listed in affected software or affected packages, you're exposed to the vulnerability. 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:
Using the .NET CLI (Command Line Interface):
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 InformationReporting Security IssuesIf 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. SupportYou 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. DisclaimerThe 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 LinksAcknowledgementsvcsjones with GitHub RevisionsV1.0 (February 10, 2026): Advisory published. Affected versions
8.0.0
8.0.1
9.0.0
9.0.1
9.0.10
9.0.11
9.0.12
9.0.2
9.0.3
9.0.4
9.0.5
9.0.6
+ 6 more Show less
9.0.7
9.0.8
9.0.9
10.0.0
10.0.1
10.0.2
Fixed in
8.0.2
9.0.13
10.0.3
References Updated Sep 10, 2026 · Source: OSV.dev |
9.0.2
patch
Dependencies (1)
|