CWE · MITRE source
CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Last updated: 20 November 2026 08: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: full · 28 mapping(s) from 5 framework(s): ATT&CK 21 (full) · ISO_IEC_27002_2022 3 (partial) · 800-53 2 (mostly) · ASVS 5.0 1 (full) · 1 (mostly)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (1)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AU-8 | Time Stamps | AU | Timestamps meeting UTC or offset standards help identify TOCTOU issues through precise chronological reconstruction of check/use operations. |
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).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-35311 KEV UPD | 9.2 | 8.8 | 0.1552 | 2023-07-11 |
CVE-2024-50379 UPD | 9.2 | 9.8 | 0.4275 | 2024-12-17 |
CVE-2025-22224 KEV UPD | 9.2 | 9.3 | 0.0156 | 2025-03-04 |
CVE-2022-36980 UPD | 8.7 | 8.1 | 0.8263 | 2023-03-29 |
CVE-2026-119977 KEV | 8.7 | 8.1 | 0.0159 | 2026-10-31 |
CVE-2024-56337 UPD | 8.5 | 9.8 | 0.1903 | 2024-12-20 |
CVE-2025-38352 KEV UPD | 8.5 | 7.8 | 0.0136 | 2025-07-22 |
CVE-2023-38146 UPD | 8.3 | 8.8 | 0.3738 | 2023-09-12 |
CVE-2025-34027 UPD | 8.3 | 9.0 | 0.4640 | 2025-05-21 |
CVE-2015-3246 KEV UPD | 8.2 | 7.4 | 0.0850 | 2015-08-11 |
CVE-2024-0132 | 8.2 | 9.0 | 0.4084 | 2024-09-26 |
CVE-2022-48618 KEV UPD | 7.9 | 7.0 | 0.0049 | 2024-01-09 |
CVE-2024-30088 KEV UPD | 7.9 | 7.0 | 0.6820 | 2024-06-11 |
CVE-2021-32708 UPD | 7.8 | 9.8 | 0.0349 | 2021-06-24 |
CVE-2019-7249 UPD | 7.7 | 9.8 | 0.0251 | 2019-01-31 |
CVE-2019-5421 UPD | 7.6 | 9.8 | 0.0156 | 2019-04-03 |
CVE-2026-44112 UPD | 7.6 | 9.6 | 0.0731 | 2026-05-06 |
CVE-2024-28718 UPD | 7.5 | 9.8 | 0.0106 | 2024-04-12 |
CVE-2024-41787 UPD | 7.5 | 9.8 | 0.0111 | 2025-01-10 |
CVE-2024-41779 UPD | 7.4 | 9.8 | 0.0083 | 2024-11-22 |
CVE-2026-25641 UPD | 7.4 | 10.0 | 0.0052 | 2026-02-06 |
CVE-2026-37531 UPD | 7.4 | 9.8 | 0.0071 | 2026-05-01 |
CVE-2024-27114 UPD | 7.3 | 9.8 | 0.0054 | 2024-09-11 |
CVE-2025-64180 UPD | 7.3 | 10.0 | 0.0033 | 2025-11-07 |
CVE-2026-64091 UPD | 7.3 | 9.8 | 0.0043 | 2026-07-19 |