Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify endpoint validating signed CMS data
-
DeliverySend crafted PKCS#7/X.509 payload
-
ExploitSignedCms.CheckSignature reparses attacker data
-
ExecutionQuadratic CPU exhaustion
-
ImpactService denial for legitimate users
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Algorithmic complexity limits
|
| Exploitation Conditions | Exploitation requires a target application that uses the System.Security.Cryptography.Pkcs package (or affected .NET Framework versions) and invokes SignedCms.CheckSignature on attacker-controlled CMS/PKCS#7 signed data containing malicious X.509 content, which triggers repeated reparsing and quadratic CPU cost. Per CVSS AV:N/AC:L/PR:N/UI:N it is remote and unauthenticated with no user interaction, but exploitation is LIMITED to deployments that actually accept and validate untrusted signed CMS messages via this API; services that never process external signed data, or that run patched versions (Pkcs 10.0.13/9.0.21/8.0.2/11.0.0-rc.2 or the listed .NET Framework updates), are not exposed. Impact is availability-only (C:N/I:N) resource exhaustion, not code execution or data disclosure. |
| Impact | Signals are consistent and point to a genuine but bounded DoS risk. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5 High) indicates a remotely reachable, low-complexity, unauthenticated attack with availability-only impact - confirmed by the dotnet/runtime GHSA advisory describing unauthenticated quadratic CPU exhaustion in SignedCms.CheckSignature. SSVC aligns: Exploitation 'none' (no observed exploitation), Automatable 'yes' (the trigger is a single crafted message that scales), Technical Impact 'partial' (service degradation, not full compromise), which matches C:N/I:N but tempers A:H since the impact is resource exhaustion rather than system takeover. No EPSS score, no POC, and no CISA KEV entry are present, so this is 'no public exploit identified at time of analysis' - not weaponized or in-the-wild. Net: a credible, automatable DoS worth prioritizing for any service that validates attacker-supplied CMS/PKCS#7 signatures, but its real-world blast radius is gated by whether an application actually exposes SignedCms.CheckSignature to untrusted input, so it is not a drop-everything issue for most deployments. Note: the input Tag 'Authentication Bypass' conflicts with the CWE-407 (Inefficient Algorithmic Complexity) classification and the advisory - this is a denial-of-service issue, not an auth bypass; treat that tag as erroneous. |
| Exploit ScenarioDerived | An attacker sends a specially crafted CMS/PKCS#7 signed message containing malicious X.509 data to a .NET service that verifies signatures via SignedCms.CheckSignature. The method repeatedly reparses the attacker-controlled certificate data, driving quadratic CPU consumption that exhausts the host and denies service to legitimate users. No authentication or user interaction is required (AV:N/AC:L/PR:N/UI:N), and no public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Unauthenticated remote attackers can drive CPU exhaustion in .NET applications that validate untrusted signed CMS/PKCS#7 data, because SignedCms.CheckSignature in the System.Security.Cryptography.Pkcs package repeatedly reparses attacker-controlled X.509 content at quadratic cost (CWE-407, CVSS 7.5, AV:N/AC:L/PR:N/UI:N with availability-only impact, C:N/I:N/A:H). Affected build ranges are System.Security.Cryptography.Pkcs 8.0.0 through 8.0.1, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, along with the listed .NET Framework 3.5 / 4.6.2 / 4.7 / 4.7.1 / 4.7.2 / 4.8 / 4.8.1 servicing baselines and Visual Studio 2022 17.14 and Visual Studio 2026 18.10. Exploitation is bounded to services that actually accept and cryptographically verify externally supplied signed CMS messages through this API; no public exploit identified at time of analysis, and CISA SSVC records exploitation as none.
RemediationAI
Vendor-released patch: System.Security.Cryptography.Pkcs 10.0.13, 9.0.21, 8.0.2, and 11.0.0-rc.2 for the corresponding affected ranges; also install the current .NET runtime/SDK (Visual Studio will prompt for the update, which brings the SDK along) and apply the .NET Framework servicing updates for the listed baselines (3.5 fixed at 2.0.50727.9188 and 3.0.30729.9171; 4.6.2/4.7/4.7.1/4.7.2 at 4.7.4150.0; 4.8 at 4.8.4811.0; 4.8.1 at 4.8.9363.0) plus Visual Studio 2022 17.14.42 and Visual Studio 2026 18.10.4. Update package references explicitly in any application that references the package, and note that self-contained deployments must be rebuilt and redeployed because they do not pick up machine-wide runtime updates; restart applications after patching. Where patching must be staged, compensating controls that reduce the attack surface are: reject or cap the size and certificate count of inbound CMS/PKCS#7 blobs before calling SignedCms.CheckSignature (trade-off: legitimately large signed messages may be refused), refuse deeply nested or duplicated X.509 certificate structures at the edge proxy or API gateway (trade-off: requires custom validation logic and can break unusual but valid encodings), rate-limit and concurrency-cap the endpoint that performs verification (trade-off: slows throughput for legitimate callers and does not stop a determined flood), and run signature validation in a worker pool with per-request CPU time budgets so exhaustion is contained rather than taking down the main service (trade-off: added latency and operational complexity). Reference advisories: https://github.com/dotnet/runtime/security/advisories/GHSA-846f-f764-76mx, https://github.com/dotnet/announcements/issues/468, https://github.com/dotnet/runtime/issues/135703, and https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-84008.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 6 packages in nuget, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw sits in the Cryptography.Pkcs library, the managed implementation of CMS/PKCS#7 signed-data handling used by SignedCms.CheckSignature. CWE-407 (Inefficient Algorithmic Complexity) describes the root cause: when verifying a signature, the parser re-walks and re-parses attacker-supplied X.509 certificate and SignedData structures on each pass instead of caching the parse, so a crafted message with many nested or repeated certificate entries multiplies the work per validation and yields quadratic CPU consumption. The CVSS vector confirms this is remote (AV:N), low-complexity (AC:L), unauthenticated (PR:N), and requires no user interaction (UI:N), with scope unchanged and impact confined to availability (A:H) - there is no code execution, memory corruption, signature forgery, or data disclosure component, and no authentication bypass despite a source metadata tag of 'Authentication Bypass' that does not match the assessed vector. The affected code ships in two forms: as the NuGet package System.Security.Cryptography.Pkcs (ranges >= 8.0.0 <= 8.0.1, >= 9.0.0 <= 9.0.20, >= 10.0.0 <= 10.0.12, and >= 11.0.0-preview.1 <= 11.0.0-rc.1) and as .NET Framework assemblies on Windows, with Visual Studio 2022 17.14 and Visual Studio 2026 18.10 bundling affected SDK/runtime baselines. EUVD enumerates the matching .NET Framework build ranges (for example .NET Framework 3.5 below 2.0.50727.9188 / 3.0.30729.9171, 4.6.2-4.7.2 below 4.7.4150.0, 4.8 below 4.8.4811.0, and 4.8.1 below 4.8.9363.0). Any deployment whose request path feeds untrusted DER/PEM signed blobs into CheckSignature - timestamp/token validators, signed-email or S/MIME gateways, signed document ingestion, certificate-chaining endpoints - is exposed regardless of host OS (Windows, Linux, macOS, all architectures).
Know when .NET gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Unauthenticated remote attacker sends one crafted CMS message (AV:N/AC:L/PR:N/UI:N); availability-only CPU exhaustion gives A:H with C:N/I:N and no scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Inefficient algorithmic complexity in .NET allows an unauthorized attacker to deny service over a network.
Technical POC Analysis
Bug class: CWE-407 (Inefficient Algorithmic Complexity).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
A high-severity availability flaw in Microsoft's System.Security.Cryptography.Pkcs library lets an unauthenticated attacker exhaust CPU on any .NET or .NET Framework application that cryptographically verifies externally supplied signed CMS/PKCS#7 messages, potentially stalling or taking those services offline. Exposure is confined to services that actually accept and validate untrusted signed CMS data - for example S/MIME or secure-message gateways, signed-document intake pipelines, and token or license processors - where a single crafted message can consume disproportionate server resources. Because the library ships inside the .NET runtime, multiple .NET Framework servicing baselines, and Visual Studio 2022/2026, leadership should expect a cross-team remediation effort spanning application dependencies and developer tooling rather than a single platform update.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) compo
Changjetong T+ (through 16.x) has .NET deserialization RCE in an AjaxPro endpoint. Attacker-controlled JSON triggers des
SQL injection (CWE-89) in Marten, the .NET transactional document DB and event store for PostgreSQL, affects versions 7.
Argument injection in the CliInvoke .NET process-wrapping library (and its former identity, AlastairLundy.CliInvoke) all
SD.NET RIM versions before 4.7.3c contain a SQL injection vulnerability that allows attackers to inject malicious SQL st
PowerDocu versions prior to 2.4.0 allow arbitrary .NET object instantiation and code execution through unsafe deserializ
Weak authentication in ASP.NET Core & Visual Studio allows an unauthorized attacker to elevate privileges over a net
NanaZip versions 5.0.1252.0 through 6.0.1629.0 contain an out-of-bounds heap read in the .NET Single File bundle parser
Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disc
DotNetNuke 9.5 contains a persistent cross-site scripting vulnerability that allows normal users to upload malicious XML
Asp.Net-Core-Inventory-Order-Management-System versions up to 9.20250118. contains a security vulnerability (CVSS 6.3).
Remote code execution in the ActiveMQ NMS AMQP .NET client affects all releases up to and including 2.3.0 when the clien
EUVD-2026-100199
GHSA-846f-f764-76mx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB