Security Resilience

CVE-2026-70186

Published
13 October 2026
Modified
13 October 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0085 57th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-70186 is a high-severity Deadlock (CWE-833) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Deadlock in ASP.NET Core allows an unauthorized attacker to deny service over a network.

CWE(s)
CWE-833

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
attack.mitre.org →
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
attack.mitre.org →
T1016.002 Wi-Fi Discovery Discovery
Adversaries may search for information about Wi-Fi networks, such as network names and passwords, on compromised systems.
attack.mitre.org →
T1021.005 VNC Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33904Shared CWE-833
CVE-2023-31084Shared CWE-833
CVE-2025-8312Shared CWE-833
CVE-2025-1713Shared CWE-833
CVE-2025-10150Shared CWE-833
CVE-2026-70616Shared CWE-833
CVE-2025-36010Shared CWE-833
CVE-2024-8447Shared CWE-833
CVE-2025-59463Shared CWE-833
CVE-2026-46352Shared CWE-833

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation partial match

Developer testing and evaluation activities can exercise concurrent paths and resource contention to discover deadlock conditions before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles applied during design can incorporate synchronization ordering, timeouts, and resource hierarchies that structurally avoid deadlock formation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices can include concurrency analysis and lock discipline to avoid deadlock conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates a secure SDLC process with checkpoints, secure coding, testing and training; none of those steps stop an existing deadlock from being exploitable, they only aim to reduce the chance one is introduced

A.8.26 Application security requirements partial match
removes
A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates establishing and applying secure engineering principles (defense-in-depth, least privilege, fail securely, security by design, etc.) and performing design reviews; deadlock is a runtime concurrency flaw in implementation or threading logic that these principles and reviews do not stop from being introduced or exploited.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate safe lock ordering, timeouts, and deadlock detection patterns.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development can detect deadlock conditions through stress and concurrency testing.

A.8.8 Management of technical vulnerabilities partial match
removes

References