Skip to main content

About CWE-367

MITRE lists these common consequences: Alter Execution Logic, Unexpected State, Modify Application Data, Modify Files or Directories, Modify Memory, Hide Activities, affecting integrity, non-repudiation.

MITRE name
Time-of-check Time-of-use (TOCTOU) Race Condition
Abstraction
Base: abstract, but detailed enough to infer detection and prevention methods
Status
Incomplete

Also Known As

  • TOCTTOU
  • TOCCTOU

Mitigations

  • The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
  • When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
  • Limit the interleaving of operations on files from multiple processes.
  • If you cannot perform operations atomically and you must share access to the resource between multiple processes or threads, then try to limit the amount of time (CPU cycles) between the check and use of the resource. This will not fix the problem, but it could make it more difficult for an attack to succeed.

Detection
MITRE lists these detection methods: Automated Static Analysis (high).

CWE-367 in the KEV Catalog

as of 2026-11-16
All KEV statistics→
  • 7 CISA KEV entries name Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) in their CVE record, tied for 39th among the 195 weaknesses named in the catalog.
  • CISA added 2 CWE-367 entries to the KEV catalog in 2024, 2 in 2025, and 2 so far in 2026.
  • Microsoft has the most CWE-367 entries in the CISA KEV catalog (2).

Related Attack Patterns

2 CAPEC patterns
CAPEC-29Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race ConditionsStandard · Severity High · Likelihood High
CAPEC-27Leveraging Race Conditions via Symbolic LinksDetailed · Severity High · Likelihood Medium

CWE-367 Vulnerabilities

8 CVEs
CVECVSS
CVE-2026-119977KEV
WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution
8.1
CVE-2015-3246KEV
Red Hat Libuser Race Condition Vulnerability
7.4
CVE-2025-38352KEV
posix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()
7.8
CVE-2025-22224KEV
VMware ESXi and Workstation TOCTOU Race Condition Vulnerability
9.3
CVE-2024-30088KEV
Windows Kernel Elevation of Privilege Vulnerability
7.0
CVE-2022-48618KEV
Apple Multiple Products Memory Corruption Vulnerability
7.0
CVE-2023-35311KEV
Microsoft Outlook Security Feature Bypass Vulnerability
8.8
CVE-2026-44112
OpenClaw < 2026.4.22 - Symlink Swap Race Condition in OpenShell FS Bridge Writes
9.6

Frequently Asked Questions

What is CWE-367?→

CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) is a MITRE CWE entry. 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.

How many exploited vulnerabilities are classified as CWE-367?→

This database lists 8 CVE records mapped to CWE-367 by their CVE Numbering Authority. 7 of them are in the CISA Known Exploited Vulnerabilities catalog, and CISA links 1 to known ransomware campaigns. Examples include CVE-2026-119977, CVE-2015-3246, CVE-2025-38352.

Weakness description, consequences, and mitigations from the CWE List, © The MITRE Corporation, used under the CWE Terms of Use. CWE mappings come from each CVE record's CNA. Exploited-in-the-wild data from the CISA KEV catalog (CC0). This site is not affiliated with or endorsed by MITRE or CISA. Attack patterns from CAPEC 3.9, © The MITRE Corporation, used under the CAPEC Terms of Use.