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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

561 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, Other Alter Execution Logic, Unexpected State
The attacker can gain access to otherwise unauthorized resources.
Integrity, Other Modify 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, Other Other
The resource in question, or other resources (through the corrupted one), may be changed in undesirable ways by a malicious user.
Non-Repudiation Hide 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, Other Other
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)
Implementation 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.
Implementation 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.
Architecture and Design Limit the interleaving of operations on files from multiple processes.
Implementation, Architecture and Design 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.
Implementation Recheck 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 ID Title CVSS Severity Published
CVE-2026-84009 Windows Projected File System Tampering Vulnerability — Windows 10 Version 1809 4.7 Medium 2026-10-13
CVE-2026-83839 Windows Hyper-V Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.0 High 2026-10-13
CVE-2026-83510 Windows Setup Files Cleanup Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.0 High 2026-10-13
CVE-2026-83504 Windows SmartScreen Information Disclosure Vulnerability — Windows 11 version 23H2 4.7 Medium 2026-10-13
CVE-2026-102672 Electron: Local race condition in Squirrel.Mac update installation on macOS — electron 6.7 Medium 2026-10-13
CVE-2026-102832 JupyterLab: Command link trust prompt in JupyterLab can trust a document other than the one clicked — jupyterlab 4.2 Medium 2026-10-13
CVE-2026-108361 Privasys Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks — ra-tls-clients 7.2 High 2026-10-12
CVE-2026-108698 hyper-mcp through 0.8.3 OCI Plugin Signature Verification TOCTOU Race Condition — hyper-mcp 6.5 Medium 2026-10-11
CVE-2026-108741 Shepherd through 0.3.1 SSRF via DNS Rebinding in Citation Checker — Shepherd 3.1 Low 2026-10-11
CVE-2026-73179 Apache CXF: JPA authorization-code consume is non-atomic — Apache CXF - - 2026-10-09
CVE-2026-106451 yawkat LZ4 Java: Native library extraction to a shared temporary directory is vulnerable to file replacement by another local user — lz4-java 7.3 High 2026-10-06
CVE-2026-89430 Gitea push mirror SSRF and forced writes to internal Git hosts — Gitea - - 2026-10-06
CVE-2026-106413 Chrome<155.0.8059.39竞态条件漏洞 — Chrome - - 2026-10-06
CVE-2026-106207 Chrome <155.0.8059.39 V8竞态条件漏洞致远程代码执行 — Chrome - - 2026-10-06
CVE-2026-106405 Chrome Android < 155.0.8059.39竞态条件漏洞 — Chrome - - 2026-10-06
CVE-2026-106300 Chrome <155.0.8059.39 缓存存储竞态条件漏洞 — Chrome - - 2026-10-06
CVE-2026-106412 Chrome macOS <155.0.8059.39 竞争条件漏洞 — Chrome - - 2026-10-06
CVE-2026-93315 BuildKit proxy CA cleanup can be disrupted by build steps — BuildKit 5.8 Medium 2026-10-05
CVE-2026-105743 Docling: SSRF guard bypass in remote resource fetching (DNS rebinding / multi-record resolution; no IP validation in HTML render mode) — docling 4.0 Medium 2026-10-05
CVE-2026-105647 Ghost: Server-Side Request Forgery in Bookmark Fetching — Ghost 4.0 Medium 2026-10-05
CVE-2026-77804 Time-of-check Time-of-use (TOCTOU) Race Condition in Root Certificate Installation in Progress® Telerik® Fiddler® Classic — Progress® Telerik® Fiddler® Classic 6.6 Medium 2026-10-05
CVE-2026-105163 crossplane crossplane-runtime ImageConfig client.go Get toctou — crossplane-runtime 5.3 Medium 2026-10-04
CVE-2026-105130 LaraDashboard 1.4.0 before 1.4.8 Race Condition Bypasses Per-IP Registration Limit — laradashboard 3.7 Low 2026-10-03
CVE-2026-104474 OpenLiteSpeed before 1.9.3 Local Privilege Escalation via lsup.sh Auto-Update — openlitespeed 6.7 Medium 2026-10-02
CVE-2026-47497 NVIDIA vGPU GSP追踪组件越界访问漏洞 — Virtual GPU Manager 7.8 High 2026-09-30
CVE-2026-95344 Chrome 154 DevTools 竞态致站点隔离绕过 — Chrome - - 2026-09-29
CVE-2026-95360 Chrome 154前编辑功能竞态条件信息泄露 — Chrome - - 2026-09-29
CVE-2026-92369 Time-of-check Time-of-use (TOCTOU) Race Condition in TeamViewer Windows Installer Rollback Mechanism Leads to Local Privilege Escalation — Full Client 7.3 High 2026-09-29
CVE-2026-101088 Nezha before 2.3.1 Denial of Service via Concurrent Server Delete — nezha 5.3 Medium 2026-09-27
CVE-2026-100713 Froxlor before 2.3.12 Privilege Escalation via SSH Key Sync — froxlor 7.8 High 2026-09-26

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