Cyber Resilience

CWE · MITRE source

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Abstraction: Class · CVEs in our corpus: 2,581

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related: A race condition exists when an "interfering code sequence" can still access the shared resource, violating exclusivity. The interfering code sequence could be "trusted" or "untrusted." A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Last updated: 21 August 2026 00:24 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: mostly · 2 mapping(s) from 1 framework(s): CAPEC 2 (mostly)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A06:2025 Insecure Design.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • AU-8 Time Stamps
  • PL-6 Security-related Activity Planning
  • PR.PS-06
  • AC-10 Concurrent Session Control
Detect
Catch it (CSF Detect / Respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.4.2
  • V10.4.5
  • V15.1.3
  • V15.4.1

NIST 800-53 r5 controls that address this weakness (2)AI-assisted

Control Title Family Why it addresses this CWE
AU-8Time StampsAUAccurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.
PL-6Security-related Activity PlanningPLCoordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2021-21166 KEV 9.28.80.23852021-03-09
CVE-2024-27983 8.88.20.87212024-04-09
CVE-2020-6819 KEV 8.78.10.02982020-04-24
CVE-2020-6820 KEV 8.78.10.06302020-04-24
CVE-2024-6387 8.78.10.99512024-07-01
CVE-2015-8556 8.410.00.13372017-03-24
CVE-2023-36884 KEV 8.37.50.98932023-07-11
CVE-2016-5195 KEV 7.97.00.83522016-11-10
CVE-2022-26904 KEV 7.97.00.09822022-04-15
CVE-2025-62215 KEV7.97.00.05992025-11-11
CVE-2023-32254 7.89.80.02942023-07-10
CVE-2019-12450 7.79.80.02602019-05-29
CVE-2020-7457 7.78.10.33112020-07-09
CVE-2021-26569 7.79.80.02182021-03-12
CVE-2021-32810 7.79.80.01922021-08-02
CVE-2021-25394 KEV 7.66.40.00402021-06-11
CVE-2021-25395 KEV 7.66.40.00372021-06-11
CVE-2021-0920 KEV 7.66.40.00812021-12-15
CVE-2022-27626 7.610.00.01062022-10-20
CVE-2014-0196 KEV 7.55.50.22482014-05-07
CVE-2016-0930 7.59.80.01032016-09-18
CVE-2015-9157 7.59.80.01162018-04-18
CVE-2020-10279 7.59.80.00972020-06-24
CVE-2022-39328 7.59.80.01002022-11-08
CVE-2023-28201 7.59.80.01172023-05-08