Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-367 (检查时间与使用时间(TOCTOU)的竞争条件) — Vulnerability Class 325

325 vulnerabilities classified as CWE-367 (检查时间与使用时间(TOCTOU)的竞争条件). AI Chinese analysis included.

CWE-367 represents a logic flaw where a system verifies a resource’s state before accessing it, allowing the state to change maliciously between the verification and actual usage. Attackers typically exploit this race condition by manipulating the resource, such as swapping a file or altering permissions, during the narrow window between the check and the use. This enables unauthorized access or privilege escalation, as the application proceeds based on outdated, validated assumptions. To mitigate this vulnerability, developers must ensure atomic operations, ensuring that the check and use occur simultaneously without interruption. Implementing robust locking mechanisms, utilizing secure system calls that combine verification and access, or adopting file descriptor-based approaches can effectively prevent state changes, thereby eliminating the race condition and securing the resource against temporal manipulation.

MITRE CWE Description
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.
Common Consequences (6)
Integrity, OtherAlter Execution Logic, Unexpected State
The attacker can gain access to otherwise unauthorized resources.
Integrity, OtherModify Application Data, Modify Files or Directories, Modify Memory, Other
Race conditions such as this kind may be employed to gain read or write access to resources which are not normally readable or writable by the user in question.
Integrity, OtherOther
The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.
Non-RepudiationHide Activities
If a file or other resource is written in this method, as opposed to in a valid way, logging of the activity may not occur.
Non-Repudiation, OtherOther
In some cases it may be possible to delete files a malicious user might not otherwise have access to, such as log files.
Mitigations (5)
ImplementationThe 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.
ImplementationWhen 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.
Architecture and DesignLimit the interleaving of operations on files from multiple processes.
Implementation, Architecture and DesignIf 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.
ImplementationRecheck the resource after the use call to verify that the action was taken appropriately.
Examples (2)
The following code checks a file, then updates its contents.
struct stat *sb; ... lstat("...",sb); // it has not been updated since the last time it was read printf("stated file\n"); if (sb->st_mtimespec==...){ print("Now updating things\n"); updateThings(); }
Bad · C
The following code is from a program installed setuid root. The program performs certain file operations on behalf of non-privileged users, and uses access checks to ensure that it does not use its root privileges to perform operations that should otherwise be unavailable the current user. The program uses the access() system call to check if the person running the program has permission to access…
if(!access(file,W_OK)) { f = fopen(file,"w+"); operate(f); ... } else { fprintf(stderr,"Unable to open file %s.\n",file); }
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2026-27189 OpenSift: Race-prone local persistence could cause state corruption/loss — OpenSift 6.6 Medium2026-02-21
CVE-2026-25738 Indico has Server-Side Request Forgery (SSRF) in multiple places — indico 7.5AIHighAI2026-02-19
CVE-2026-20796 Time-of-check time-of-use vulnerability in common teams API — Mattermost 3.1 Low2026-02-13
CVE-2026-26224 Intego Log Reporter TOCTOU Local Privilege Escalation — Log Reporter 7.0AIHighAI2026-02-12
CVE-2023-20548 AMD Graphics Driver 安全漏洞 — AMD Radeon™ RX 5000 Series Graphics Products 7.0AIHighAI2026-02-11
CVE-2023-31324 AMD Graphics Driver 安全漏洞 — AMD Radeon™ RX 5000 Series Graphics Products 7.0AIHighAI2026-02-11
CVE-2024-36311 AMD Processors 安全漏洞 — AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics 6.4AIMediumAI2026-02-10
CVE-2026-21240 Windows HTTP.sys Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2026-02-10
CVE-2026-21523 GitHub Copilot and Visual Studio Code Remote Code Execution Vulnerability — Microsoft Visual Studio Code CoPilot Chat Extension 8.0 High2026-02-10
CVE-2026-25728 ClipBucket v5 Affected by Remote Code Execution via Avatar/Background File Upload Race Condition — clipbucket-v5 8.1AIHighAI2026-02-10
CVE-2026-25641 SandboxJS has a sandbox escape via TOCTOU bug on keys in property accesses — SandboxJS 10.0 Critical2026-02-06
CVE-2025-13818 Local privilege escalation in ESET Management Agent for Windows — ESET Management Agent 7.8AIHighAI2026-02-06
CVE-2026-25052 n8n Improper File Access Controls Allow Arbitrary File Read by Authenticated Users — n8n 8.8AIHighAI2026-02-04
CVE-2026-0924 BuhoCleaner 1.15.2 - Local Privilege Escalation via PID reuse attack — BuhoCleaner 7.8AIHighAI2026-02-02
CVE-2026-24071 XPC Client Validation via PID leading to Local Privilege Escalation in Native Instruments Native Access — Native Access 8.8AIHighAI2026-02-02
CVE-2026-23988 Rufus has Local Privilege Escalation via TOCTOU Race Condition in Fido Script Handling — rufus 7.3 High2026-01-22
CVE-2026-22281 Dell PowerScale OneFS 安全漏洞 — PowerScale OneFS 3.5 Low2026-01-22
CVE-2026-1035 Org.keycloak.protocol.oidc: keycloak refresh token reuse bypass via toctou race condition — Red Hat build of Keycloak 26.4 3.1 Low2026-01-21
CVE-2026-21912 Junos OS: MX10k Series: 'show system firmware' CLI command may lead to LC480 or LC2101 line card reset — Junos OS 5.5 Medium2026-01-15
CVE-2026-22820 Outray cli is vulnerable to race conditions in tunnels creation — outray 5.3AIMediumAI2026-01-14
CVE-2026-20831 Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-01-13
CVE-2026-20816 Windows Installer Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-01-13
CVE-2026-20809 Windows Kernel Memory Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-01-13
CVE-2025-47344 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera Driver — Snapdragon 6.7 Medium2026-01-06
CVE-2025-47332 Time-of-check Time-of-use (TOCTOU) Race Condition in Camera Driver — Snapdragon 6.7 Medium2026-01-06
CVE-2025-69211 Nest has a Fastify URL Encoding Middleware Bypass (TOCTOU) — nest 8.1 -2025-12-29
CVE-2025-64645 Multiple Vulnerabilities in IBM Concert Software. — Concert 7.7 High2025-12-26
CVE-2025-62004 BullWall Server Intrusion Protection (SIP) initialization race condition — Server Intrusion Protection 7.5 High2025-12-18
CVE-2025-62003 BullWall Server Intrusion Protection RDP MFA connection delay — Server Intrusion Protection 7.5 High2025-12-18
CVE-2025-68146 filelock has TOCTOU race condition that allows symlink attacks during lock file creation — filelock 6.3 Medium2025-12-16

Vulnerabilities classified as CWE-367 (检查时间与使用时间(TOCTOU)的竞争条件) represent 325 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.