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: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (2)AI
| 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-2016-5195 KEV | 9.1 | 7.0 | 0.9418 | 2016-11-10 |
CVE-2023-36884 KEV | 9.1 | 7.5 | 0.9322 | 2023-07-11 |
CVE-2018-15473 | 6.5 | 5.3 | 0.9036 | 2018-08-17 |
CVE-2022-46689 | 6.5 | 7.0 | 0.8555 | 2022-12-15 |
CVE-2017-1000112 | 6.4 | 7.0 | 0.8286 | 2017-10-05 |
CVE-2024-27983 | 6.2 | 8.2 | 0.7593 | 2024-04-09 |
CVE-2014-0196 KEV | 6.0 | 5.5 | 0.4856 | 2014-05-07 |
CVE-2021-21166 KEV | 6.0 | 8.8 | 0.3798 | 2021-03-09 |
CVE-2016-1757 | 4.9 | 7.0 | 0.5845 | 2016-03-24 |
CVE-2022-26904 KEV | 4.7 | 7.0 | 0.2159 | 2022-04-15 |
CVE-2014-0226 | 4.5 | 0.0 | 0.7544 | 2014-07-20 |
CVE-2024-6387 | 4.5 | 8.1 | 0.4806 | 2024-07-01 |
CVE-2020-7457 | 4.3 | 8.1 | 0.4458 | 2020-07-09 |
CVE-2019-0217 | 4.1 | 7.5 | 0.4302 | 2019-04-08 |
CVE-2017-2619 | 3.9 | 7.5 | 0.4067 | 2018-03-12 |
CVE-2020-6820 KEV | 3.8 | 8.1 | 0.0313 | 2020-04-24 |
CVE-2016-8655 | 3.7 | 7.8 | 0.3492 | 2016-12-08 |
CVE-2020-6819 KEV | 3.6 | 8.1 | 0.0036 | 2020-04-24 |
CVE-2020-9839 | 3.6 | 7.0 | 0.3589 | 2020-06-09 |
CVE-2021-30955 | 3.6 | 7.0 | 0.3627 | 2021-08-24 |
CVE-2025-62215 KEV | 3.5 | 7.0 | 0.0237 | 2025-11-11 |
CVE-2007-0099 | 3.4 | 0.0 | 0.5654 | 2007-01-08 |
CVE-2015-8556 | 3.3 | 10.0 | 0.2121 | 2017-03-24 |
CVE-2018-4192 | 3.3 | 7.5 | 0.3041 | 2018-06-08 |
CVE-2021-25394 KEV | 3.3 | 6.4 | 0.0043 | 2021-06-11 |