Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify endpoint decoding CMS/PKCS#7
-
DeliveryCraft malicious CMS attribute set
-
ExploitSubmit crafted request pre-authentication
-
ExecutionTrigger quadratic work in EnvelopedCms.Decode
-
ImpactCPU exhaustion denies service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Asymmetric resource consumption control
|
| Exploitation Conditions | Exploitable only against Windows-hosted .NET applications that reference a vulnerable System.Security.Cryptography.Pkcs version (>=8.0.0<=8.0.1, >=9.0.0<=9.0.20, >=10.0.0<=10.0.12, or 11.0.0-preview.1 through 11.0.0-rc.1) AND that pass attacker-controlled data to EnvelopedCms.Decode while processing PKCS#7/CMS enveloped messages. The attacker needs no authentication or user interaction and can reach it pre-auth over the network, but exploitation is LIMITED by: Windows platform only (the GHSA states non-Windows is not affected); the application must actually expose and invoke the CMS/PKCS#7 decode code path on untrusted input (many .NET web apps never do); and high attack complexity (AC:H) since the request payload must be specifically crafted to force quadratic resource consumption. |
| Impact | This is a moderate-severity denial-of-service issue (CVSS 5.9, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) with impact limited strictly to availability (A:H; C:N/I:N) - there is no code execution or data exposure. The signals are internally consistent and point AWAY from urgent priority: the network vector and lack of required privileges or user interaction (AV:N/PR:N/UI:N) are offset by high attack complexity (AC:H), reflecting that the attacker must craft CMS/PKCS#7 attributes that trigger quadratic processing in EnvelopedCms.Decode and the target app must actually invoke that decode path on untrusted input. CISA's SSVC framework reinforces a low-urgency posture: Exploitation=none, Automatable=no, Technical Impact=partial. There is no CISA KEV listing and no public exploit identified at time of analysis. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. The one tension to note: the generic NVD/MSRC description frames this as a broad '.NET web application' DoS via 'web requests,' while the authoritative dotnet/runtime GHSA advisory scopes it precisely to Windows-only applications that call EnvelopedCms.Decode on attacker-supplied PKCS#7/CMS data - a much narrower exposure than the description implies. Treat the GHSA scoping as authoritative. Net: a real but low-priority, patch-in-normal-cycle issue, not an emergency. |
| Exploit ScenarioDerived | A .NET web application running on Windows exposes an endpoint that decodes attacker-supplied PKCS#7/CMS data (e.g. validating an uploaded signed/enveloped message) using a vulnerable System.Security.Cryptography.Pkcs version. A remote, unauthenticated attacker submits specially crafted CMS attributes that force EnvelopedCms.Decode into quadratic-time processing, exhausting CPU and degrading or halting the service before authentication. No public exploit code has been identified at time of analysis; attack complexity is high because the payload must be shaped to trigger the quadratic path and the app must actually reach the vulnerable decode call. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
A pre-authentication denial-of-service condition in the .NET cryptographic library System.Security.Cryptography.Pkcs causes CPU exhaustion on Windows when EnvelopedCms.Decode processes specially crafted CMS/PKCS#7 attribute sets, because the decoding routine performs quadratic work proportional to the number of attacker-supplied attributes rather than linear work. Affected applications are Windows-hosted .NET apps that reference a vulnerable package version (8.0.0-8.0.1, 9.0.0-9.0.20, 10.0.0-10.0.12, or 11.0.0-preview.1 through 11.0.0-rc.1) and pass untrusted PKCS#7/CMS enveloped data into the decode path - a pattern common in S/MIME mail gateways, signed-message web endpoints, and certificate/token processing services; there is no impact to confidentiality or integrity (CVSS 5.9, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-405). Exploitation requires no authentication or user interaction but is constrained by the Windows-only scope, the requirement that the vulnerable CMS decode path actually be reachable from untrusted input, and high attack complexity (AC:H) needed to tune payloads for meaningful amplification; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', and no public exploit identified at time of analysis, though vendor-released patches are available. Visual Studio 2022 (17.14.0-17.14.41) and Visual Studio 2026 (18.10.0-18.10.3) installations that bundle the affected SDK/runtime are also in scope.
RemediationAI
Vendor-released patches are available: upgrade the System.Security.Cryptography.Pkcs package reference to 8.0.2 (8.0.x line), 9.0.21 (9.0.x line), 10.0.13 (10.0.x line), or 11.0.0-rc.2 (11.0.0 preview line), then rebuild and redeploy - note that self-contained applications do not pick up runtime servicing automatically and must update the package reference explicitly, and running apps must be restarted for the change to take effect. Install the latest .NET SDK/runtime; if SDKs were installed through Visual Studio, update Visual Studio itself to 17.14.42 or later (2022 line) or 18.10.4 or later (2026 line), which also refreshes the bundled .NET SDKs. Developers should confirm current package versions with dotnet --info and dotnet list package --include-transitive. Where immediate patching is not possible, the highest-value compensating control is to prevent untrusted input from reaching EnvelopedCms.Decode: reject or strip unusually large attribute sets at the application or reverse-proxy layer before decoding, cap request body sizes and attribute counts (WAF or middleware limits), and front the CMS-decoding endpoints with rate limiting and per-request CPU/time budgets so that any quadratic amplification is bounded; the trade-off is that well-formed but attribute-heavy legitimate CMS messages (large S/MIME certificate chains, many countersignatures) may be rejected, so thresholds must be tuned against real traffic. Because exploitation is Windows-only, hosting the affected workload on Linux/macOS is reported by the vendor as not vulnerable, but that is a platform migration rather than a security control and should not be treated as a substitute for patching. Monitor MSRC's update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70162) and GHSA-2fmv-rv2c-59x7 (https://github.com/dotnet/runtime/security/advisories/GHSA-2fmv-rv2c-59x7) for any revision; per vendor data there is no vendor-released patch gap, and CISA's SSVC records no known exploitation and a non-automatable attack, so prioritization can follow normal patch cycles while exposure through public CMS-decoding endpoints is verified.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 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 lives in .NET's CMS/PKCS#7 message decoding stack, specifically the System.Security.Cryptography.Pkcs NuGet package's implementation of EnvelopedCms.Decode. CMS (Cryptographic Message Syntax, RFC 5652) enveloped messages carry attributes such as signed attributes, countersignatures, or arbitrary content-type attributes inside authenticated and unauthenticated attribute sets; a decoder must walk these structures to validate and index them. Per GHSA-2fmv-rv2c-59x7, on Windows the decoder performs work that grows quadratically with the number of attacker-supplied attributes, so a modestly sized request containing many attributes triggers disproportionate CPU consumption - a classic CWE-405 asymmetric resource consumption / amplification pattern rather than a memory-safety or logic flaw. The vulnerability is platform-scoped: the advisory explicitly states the affected platforms are Windows (all architectures) and that non-Windows platforms are not affected, so the root cause is in a Windows-specific code path within the shared runtime package. Because the defect sits in a library rather than in an application framework, exposure is entirely a function of whether the hosting application invokes the decode routine on attacker-reachable data; the CVSS vector's AC:H reflects the crafting precision required to force the quadratic blowup, while PR:N confirms the decode path can be reached without credentials. The .NET runtime repository (dotnet/runtime issue 135699) and the .NET announcements repository (issue 454) track the fix.
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:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Remote pre-auth reachable (AV:N/PR:N/UI:N) but AC:H because the app must invoke the CMS decode path and the payload must be crafted to force quadratic work; availability-only impact (A:H, C/I:N).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
A denial of service vulnerability exists when Microsoft Common Object Runtime Library improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET web application. A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET application. The update addresses the vulnerability by correcting how the .NET web application handles web requests.
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
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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-100402
GHSA-2fmv-rv2c-59x7
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB