CVE-2026-84008: .NET Denial of Service Vulnerability

Published Oct 13, 2026
·
Updated

.NET Denial of Service Vulnerability

Other sources

Executive summary

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

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/468

CVSS Details

- 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) Affected Platforms

- Platforms: Windows, Linux, macOS - Architectures: All

<a name="affected-packages"></a>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.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

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

If using a package listed in affected packages, you're exposed to the vulnerability.

<a name="how-fix"></a>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 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.

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

CVE-2026-84008

Acknowledgements

- Dr.-Ing Ashar Javed (@soaj1664ashar)

Revisions

V1.0 (10/13/2026): Advisory published.

— GitHub

Inefficient algorithmic complexity in .NET allows an unauthorized attacker to deny service over a network.

— Microsoft

Affected Software

37 affected componentsFixes available
Microsoft .NET Framework=4.8.1
4.8.9363.0
nuget/system.security.cryptography.pkcs>=9.0.0<=9.0.20
9.0.21
nuget/system.security.cryptography.pkcs>=8.0.0<=8.0.1
8.0.2
nuget/system.security.cryptography.pkcs>=11.0.0-preview.1<=11.0.0-rc.1
11.0.0-rc.2
nuget/system.security.cryptography.pkcs>=10.0.0<=10.0.12
10.0.13
Microsoft System.Security.Cryptography.Pkcs<10.0.13
10.0.13
Microsoft System.Security.Cryptography.Pkcs<8.0.2
8.0.2
Microsoft System.Security.Cryptography.Pkcs<9.0.21
9.0.21
Microsoft System.Security.Cryptography.Pkcs<11.0.0-rc.2
11.0.0-rc.2
Microsoft .NET Framework=3.5, =4.8.1, >=2.0.50727<2.0.50727.9188, >=3.0.30729<3.0.30729.9171
2.0.50727.91883.0.30729.91714.8.9363.0
Microsoft .NET Framework=3.5, =4.8.1, >=2.0.50727<2.0.50727.9188, >=3.0.30729<3.0.30729.9171
2.0.50727.91883.0.30729.91714.8.10008.0
Microsoft .NET Framework=3.5, =4.8.1, >=2.0.50727<2.0.50727.9188, >=3.0.30729<3.0.30729.9171
2.0.50727.91883.0.30729.91714.8.9363.0
Microsoft .NET Framework=3.5, =4.8.1, >=2.0.50727<2.0.50727.9188, >=3.0.30729<3.0.30729.9171
2.0.50727.91883.0.30729.91714.8.9363.0
Microsoft Visual Studio 2022>=17.14<17.14.42
17.14.42
Microsoft .NET Framework>=4.8<4.8.4811.0
4.8.4811.0
Microsoft .NET Framework>=4.8<4.8.4811.0
4.8.4811.0
Microsoft .NET Framework=4.6.2, >=4.7<4.7.4150.0, =4.7.1, =4.7.2
4.7.4150.0
Microsoft .NET Framework>=4.8<4.8.4811.0
4.8.4811.0
Microsoft .NET Framework=3.5, >=4.8<4.8.4811.0, >=2.0.50727<2.0.50727.9188, >=3.0.30729<3.0.30729.9171
2.0.50727.91883.0.30729.91714.8.4811.0
Microsoft .NET Framework=3.5, >=4.8<4.8.4811.0, >=2.0.50727<2.0.50727.9188, >=3.0.30729<3.0.30729.9171
2.0.50727.91883.0.30729.91714.8.4811.0
Microsoft .NET Framework=4.6.2, >=4.7<4.7.4150.0, =4.7.1, =4.7.2
4.7.4150.0
Microsoft .NET Framework=3.5, =4.6.2, >=4.7<4.7.4150.0, =4.7.1, =4.7.2, >=2.0.50727<2.0.50727.8987, >=3.0.30729<3.0.30729.8982
2.0.50727.89873.0.30729.89824.7.4150.0
Microsoft .NET Framework=3.5, >=4.8<4.8.4811.0, >=2.0.50727<2.0.50727.9073, >=3.0.30729<3.0.30729.9070
2.0.50727.90733.0.30729.90704.8.4811.0
Microsoft .NET Framework=3.5, =4.6.2, >=4.7<4.7.4150.0, =4.7.1, =4.7.2, >=2.0.50727<2.0.50727.9073, >=3.0.30729<3.0.30729.9070
2.0.50727.90733.0.30729.90704.7.4150.0
Microsoft .NET Framework=3.5, =4.7.2, >=2.0.50727<2.0.50727.9073, >=3.0.30729<3.0.30729.9070
2.0.50727.90733.0.30729.90704.7.4150.0
Microsoft .NET Framework=3.5, >=2.0.50727<2.0.50727.9188, >=3.0.30729<3.0.30729.9171
2.0.50727.91883.0.30729.9171
Microsoft .NET Framework=3.5, >=2.0.50727<2.0.50727.8987, >=3.0.30729<3.0.30729.8982
2.0.50727.89873.0.30729.8982
Microsoft .NET Framework=3.5, >=2.0.50727<2.0.50727.8987, >=3.0.30729<3.0.30729.8982
2.0.50727.89873.0.30729.8982
Microsoft Visual Studio 2026>=18.10<18.10.4
18.10.4
alpine/dotnet10-runtime<10.0.13-r0
10.0.13-r0
alpine/dotnet10-runtime<10.0.13-r0
10.0.13-r0
alpine/dotnet8-runtime<8.0.32-r0
8.0.32-r0
alpine/dotnet8-runtime<8.0.32-r0
8.0.32-r0
alpine/dotnet8-runtime<8.0.32-r0
8.0.32-r0
alpine/dotnet9-runtime<9.0.21-r0
9.0.21-r0
alpine/dotnet9-runtime<9.0.21-r0
9.0.21-r0
alpine/dotnet9-runtime<9.0.21-r0
9.0.21-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.9363.0Patch KB5127691
  2. Upgrade

    Upgrade nuget/System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 9.0.21
  3. Upgrade

    Upgrade nuget/System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 8.0.2
  4. Upgrade

    Upgrade nuget/System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 11.0.0-rc.2
  5. Upgrade

    Upgrade nuget/System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 10.0.13
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.13
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.0.2
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.0.21
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 11.0.0-rc.2
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Fixed in 4.8.9363.0Patch KB5127692
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Fixed in 4.8.10008.0Patch KB5127694
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Fixed in 4.8.9363.0Patch KB5127690
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Fixed in 4.8.9363.0Patch KB5127689
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Fixed in 4.8.9363.0Patch KB5127693
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.14.42
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4811.0Patch KB5127684
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4811.0Patch KB5127688
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.7.4150.0Patch KB5127668
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Fixed in 4.8.4811.0Patch KB5127687
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.8.4811.0Patch KB5127686
  21. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Fixed in 4.8.4811.0Patch KB5127683
  22. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.7.4150.0Patch KB5127667
  23. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9073Fixed in 3.0.30729.9070Fixed in 4.8.4811.0Patch KB5127685
  24. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8987Fixed in 3.0.30729.8982Fixed in 4.7.4150.0Patch KB5126868
  25. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9073Fixed in 3.0.30729.9070Fixed in 4.7.4150.0Patch KB5127666
  26. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.9188Fixed in 3.0.30729.9171Patch KB5127696
  27. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8987Fixed in 3.0.30729.8982Patch KB5127664
  28. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.50727.8987Fixed in 3.0.30729.8982Patch KB5127660
  29. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.10.4
  30. Upgrade

    Upgrade System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 10.0.13
  31. Upgrade

    Upgrade System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 11.0.0-rc.2
  32. Upgrade

    Upgrade System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 8.0.2
  33. Upgrade

    Upgrade System.Security.Cryptography.Pkcs to a version that resolves this vulnerability.

    Fixed in 9.0.21
  34. Operational

    Recompile and redeploy self-contained applications targeting any impacted versions.

  35. Operational

    Restart applications after installing the updated runtime or SDK so the update takes effect.

Event History

Oct 13, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·07:01 PM
Data Sourced
via MITRE·07:01 PM
DescriptionSeverity
Data Sourced
via NVD·07:20 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·07:20 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·08:03 PM
Data Sourced
via GitHub·08:03 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which applications are exposed?

Microsoft .NET projects using an affected version of System.Security.Cryptography.Pkcs are affected if they invoke SignedCms.CheckSignature on attacker-controlled X.509 data. The advisory applies across Windows, Linux, and macOS on all architectures.

2

Does exploitation require authentication or user interaction?

No. The CVSS vector indicates network reachability, low attack complexity, no privileges required, and no user interaction.

3

What is the expected impact of a successful attack?

An attacker can cause repeated parsing of supplied X.509 data, resulting in quadratic CPU consumption and denial of service. The listed CVSS impacts indicate availability impact only, with no confidentiality or integrity impact.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203