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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

413 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-62728 Windows Common Log File System Driver Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.0 High2026-08-11
CVE-2026-6505 Axis ACAP框架TOCTOU漏洞致权限提升 — AXIS OS 5.1 Medium2026-08-11
CVE-2026-5303 ACAP unsigned应用安装TOCTOU漏洞 — AXIS OS 5.7 Medium2026-08-11
CVE-2026-72584 fastschema - TOCTOU Race Condition Bypasses OTP Attempt Limit in Account Recovery — fastschema 7.4 High2026-08-10
CVE-2026-19079 Policycoreutils: policycoreutils: toctou race condition in fixfiles allows arbitrary selinux label manipulation — Red Hat Hardened Images 4.4 Medium2026-08-07
CVE-2026-57818 Apache CXF: OAuth2 Authorization Code Replay via TOCTOU in JCacheCodeDataProvider — Apache CXF--2026-08-06
CVE-2026-55524 PraisonAI: SSRF in web_crawl tool via redirect-following and DNS rebinding (validate-then-fetch gap) — PraisonAI 7.5 High2026-08-05
CVE-2026-70597 Electron: Parent process code-sign check is spoofable — electron 6.3 Medium2026-08-05
CVE-2026-71272 Memos Webhook DNS Rebinding TOCTOU SSRF in safeDialContext() — memos 8.5 High2026-08-05
CVE-2026-71210 mealie - DNS-Rebinding TOCTOU in SSRF Guard Allows Internal Network and Cloud Metadata Access — mealie 5.3 Medium2026-08-05
CVE-2026-54020 Open WebUI: DNS Rebinding SSRF Bypass — open-webui 6.3 Medium2026-08-04
CVE-2026-47621 NVIDIA Dynamo 竞争条件问题漏洞 — Dynamo 6.5 Medium2026-08-04
CVE-2026-58041 Node.js 竞争条件问题漏洞 — node--2026-08-04
CVE-2026-11835 Caliptra Update-Reset Secure-Boot Bypass via Attacker-Chosen AXI Staging Address (TOCTOU) — Core ROM 5.6 Medium2026-08-04
CVE-2026-66314 Microsoft Edge (Chromium-based) Information Disclosure Vulnerability — Microsoft Edge (Chromium-based) 6.5 Medium2026-08-03
CVE-2026-47746 Misskey: JSON-LD signature validation + compaction is vulnerable to timing attacks — misskey 8.9 High2026-08-03
CVE-2026-18477 Tar: tar: toctou in incremental dumpdir 'x' rename handling allows restore path escape — Red Hat Hardened Images 4.4 Medium2026-08-03
CVE-2026-20492 MediaTek Chipsets 竞争条件问题漏洞 — MediaTek chipset--2026-08-03
CVE-2026-20474 MediaTek Chipsets 竞争条件问题漏洞 — MediaTek chipset--2026-08-03
CVE-2026-67607 LightFTP 2.3.1 Race Condition DoS via worker_thread_cleanup — LightFTP 5.9 Medium2026-07-31
CVE-2026-13113 Time-of-check Time-of-use (TOCTOU) Race Condition in GitLab — GitLab 6.5 Medium2026-07-29
CVE-2026-56822 Netty: TOCTOU in OcspServerCertificateValidator — netty 7.4 High2026-07-28
CVE-2026-59676 Local File Deletion Attack Vector in rm_rf() in seunshare — selinux 5.8 Medium2026-07-23
CVE-2026-65598 n8n before 1.123.64 Remote Code Execution via Git Clone — n8n--2026-07-22
CVE-2026-16082 Sipeed PicoClaw pipeline_execute.go ExecTool.executeRun toctou — PicoClaw 5.3 Medium2026-07-18
CVE-2026-54242 Statamic: Server-Side Request Forgery via Glide (DNS rebinding) — cms 4.9 Medium2026-07-17
CVE-2026-62212 OpenClaw < 2026.5.28 Authentication Bypass via safeFetch — OpenClaw 7.1 High2026-07-17
CVE-2026-53410 Zoom Clients for Windows - Race Condition — Zoom Clients 7.0 High2026-07-16
CVE-2026-15449 TOCTOU double copyin in illumos dld ioctl handling causes kernel heap corruption — illumos-gate--2026-07-16
CVE-2026-45804 Diffusers: TOCTOU Trust Remote Code Bypass — diffusers 7.5 High2026-07-15

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