Live › vulnerability › CVE-2026-84008
Go to dashboardSystem.Security.Cryptography.Pkcs in .NET can be made to re-parse attacker-supplied X.509 data repeatedly inside SignedCms.CheckSignature, using quadratic CPU time. An unauthenticated remote sender can exhaust CPU and deny service to the process that verifies signed messages.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| System.Security.Cryptography.Pkcs | nuget | >= 10.0.0, <= 10.0.12 | 10.0.13 |
| System.Security.Cryptography.Pkcs | nuget | >= 11.0.0-preview.1, <= 11.0.0-rc.1 | 11.0.0-rc.2 |
| System.Security.Cryptography.Pkcs | nuget | >= 8.0.0, <= 8.0.1 | 8.0.2 |
| System.Security.Cryptography.Pkcs | nuget | >= 9.0.0, <= 9.0.20 | 9.0.21 |
Run dotnet list package --include-transitive and look for System.Security.Cryptography.Pkcs in the affected ranges: 8.0.0 to 8.0.1, 9.0.0 to 9.0.20, 10.0.0 to 10.0.12, or 11.0.0-preview.1 to 11.0.0-rc.1.
Check whether any code calls SignedCms.CheckSignature on untrusted input.
Run to see installed runtime and SDK versions.
dotnet --info8.0.2, 9.0.21, 10.0.13, or 11.0.0-rc.2 for the matching major line, then redeployEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Microsoft is releasing this security advisory to provide information about a vulnerability in System.Security.Cryptography.Pkcs. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
SignedCms.CheckSignature can repeatedly reparse attacker-controlled X.509 data, causing unauthenticated quadratic CPU exhaustion.
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/468
Version: 3.1
Severity: High
Score: 7.5
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-407 (Inefficient Algorithmic Complexity)
The vulnerability affects Microsoft .NET projects that use an affected package version listed below.
| Package name | Affected version | Patched version |
|---|---|---|
| System.Security.Cryptography.Pkcs | >= 10.0.0, <= 10.0.12 | 10.0.13 |
| System.Security.Cryptography.Pkcs | >= 11.0.0-preview.1, <= 11.0.0-rc.1 | 11.0.0-rc.2 |
| System.Security.Cryptography.Pkcs | >= 8.0.0, <= 8.0.1 | 8.0.2 |
| System.Security.Cryptography.Pkcs | >= 9.0.0, <= 9.0.20 | 9.0.21 |
If using a package listed in affected packages, you're exposed to the vulnerability.
dotnet --info 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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
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.
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.
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.
V1.0 (10/13/2026): Advisory published.
This page as .md · .json · in your agent: get_signal("CVE-2026-84008")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.