Cyber Resilience

CWE · MITRE source

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

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

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: 04 July 2026 00:28 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: full · 9 mapping(s) from 4 framework(s): ASVS 5.0 5 (full) · CAPEC 2 (mostly) · OWASP-Web 1 (partial) · ATT&CK 1 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A06:2025 Insecure Design.

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

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.

MITRE ATT&CK techniques this weakness enables

Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.

Direction: other covers this; this covers other (F/M/P = full / mostly / partial).

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2014-0196 KEV10.05.50.22482014-05-07
CVE-2016-5195 KEV10.07.00.83522016-11-10
CVE-2020-6819 KEV10.08.10.02982020-04-24
CVE-2020-6820 KEV10.08.10.06302020-04-24
CVE-2021-21166 KEV10.08.80.26522021-03-09
CVE-2021-25394 KEV10.06.40.00422021-06-11
CVE-2021-25395 KEV10.06.40.00392021-06-11
CVE-2021-0920 KEV10.06.40.00812021-12-15
CVE-2022-26904 KEV10.07.00.09822022-04-15
CVE-2023-36884 KEV10.07.50.99082023-07-11
CVE-2025-62215 KEV10.07.00.06102025-11-11
CVE-2014-02268.00.00.85742014-07-20
CVE-2018-154738.05.30.98632018-08-17
CVE-2023-281268.05.90.66662023-05-09
CVE-2024-27983 UPD8.08.20.87212024-04-09
CVE-2024-63878.08.10.99512024-07-01
CVE-2016-09307.09.80.01032016-09-18
CVE-2015-85567.010.00.13372017-03-24
CVE-2017-109157.09.00.01672017-07-05
CVE-2015-91577.09.80.01162018-04-18
CVE-2019-124507.09.80.02602019-05-29
CVE-2019-20067.09.80.00722019-06-19
CVE-2020-102797.09.80.00972020-06-24
CVE-2021-265697.09.80.02182021-03-12
CVE-2021-328107.09.80.01922021-08-02