CWE · MITRE source
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
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)
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.
NIST 800-53 r5 controls that address this weakness (2)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AU-8 | Time Stamps | AU | Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs. |
PL-6 | Security-related Activity Planning | PL | Coordination 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 UPD | 9.2 | 8.8 | 0.2385 | 2021-03-09 |
CVE-2024-27983 UPD | 8.8 | 8.2 | 0.8721 | 2024-04-09 |
CVE-2020-6819 KEV UPD | 8.7 | 8.1 | 0.0298 | 2020-04-24 |
CVE-2020-6820 KEV UPD | 8.7 | 8.1 | 0.0630 | 2020-04-24 |
CVE-2024-6387 UPD | 8.7 | 8.1 | 0.9951 | 2024-07-01 |
CVE-2015-8556 UPD | 8.4 | 10.0 | 0.1337 | 2017-03-24 |
CVE-2023-36884 KEV UPD | 8.3 | 7.5 | 0.9893 | 2023-07-11 |
CVE-2016-5195 KEV UPD | 7.9 | 7.0 | 0.8352 | 2016-11-10 |
CVE-2022-26904 KEV UPD | 7.9 | 7.0 | 0.0982 | 2022-04-15 |
CVE-2025-62215 KEV | 7.9 | 7.0 | 0.0599 | 2025-11-11 |
CVE-2023-32254 UPD | 7.8 | 9.8 | 0.0294 | 2023-07-10 |
CVE-2019-12450 UPD | 7.7 | 9.8 | 0.0260 | 2019-05-29 |
CVE-2020-7457 UPD | 7.7 | 8.1 | 0.3311 | 2020-07-09 |
CVE-2021-26569 UPD | 7.7 | 9.8 | 0.0218 | 2021-03-12 |
CVE-2021-32810 UPD | 7.7 | 9.8 | 0.0192 | 2021-08-02 |
CVE-2021-25394 KEV UPD | 7.6 | 6.4 | 0.0040 | 2021-06-11 |
CVE-2021-25395 KEV UPD | 7.6 | 6.4 | 0.0037 | 2021-06-11 |
CVE-2021-0920 KEV UPD | 7.6 | 6.4 | 0.0081 | 2021-12-15 |
CVE-2022-27626 UPD | 7.6 | 10.0 | 0.0106 | 2022-10-20 |
CVE-2014-0196 KEV UPD | 7.5 | 5.5 | 0.2248 | 2014-05-07 |
CVE-2016-0930 UPD | 7.5 | 9.8 | 0.0103 | 2016-09-18 |
CVE-2015-9157 UPD | 7.5 | 9.8 | 0.0116 | 2018-04-18 |
CVE-2020-10279 UPD | 7.5 | 9.8 | 0.0097 | 2020-06-24 |
CVE-2022-39328 UPD | 7.5 | 9.8 | 0.0100 | 2022-11-08 |
CVE-2023-28201 UPD | 7.5 | 9.8 | 0.0117 | 2023-05-08 |