What is CWE-367?
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.
CWE-367 is a base-level weakness in MITRE’s Common Weakness Enumeration, with a MITRE likelihood of exploit of Medium. Applicable platforms: Language: Not Language-Specific.
Source: MITRE CWE (CWE-367 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.
Consequences
- 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.
- Other — Unexpected State. The product may perform invalid actions when the resource is in an unexpected state.
Source: MITRE CWE, common consequences.
How CWE-367 is exploited in the wild
Threadlinqs maps 34 CVEs to CWE-367, published between 2015-08-11 and 2026-11-11. 4 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 2 are tied to ransomware campaigns. By CVSS v3 severity the set splits into 2 critical, 17 high, 7 medium, 4 low. The highest EPSS score in the set is 68.2% (CVE-2024-30088), the modelled probability of exploitation in the next 30 days. 61 tracked threats reference CWE-367 directly or through a CVE it covers; the most recent is “Google Chrome 157 Stable Update Fixes 83 Security Flaws Including 5 Critical Use-After-Free Bugs (CVE-2026-126885, CVE-2026-126895, CVE-2026-126879, CVE-2026-126846, CVE-2026-126911)” (2026-11-12). Affected products concentrate in Microsoft (7), Google (4), nodejs (3), among 20 vendors in total.
Vulnerabilities (CVEs)
All 34 CVEs mapped to CWE-367, CISA KEV first, then by CVSS score.
- CVE-2025-22224 — CISA KEV · CVSS 9.3 critical · EPSS 1.5% · published 2025-03-04
- CVE-2026-33825 — CISA KEV · CVSS 7.8 high · EPSS 0.3% · published 2026-04-14
- CVE-2015-3246 — CISA KEV · CVSS 7.4 high · EPSS 8.4% · published 2015-08-11
- CVE-2024-30088 — CISA KEV · CVSS 7 high · EPSS 68.2% · published 2024-06-11
- CVE-2026-25052 — CVSS 9.9 critical · EPSS 0.3% · published 2026-02-04
- CVE-2026-119977 — CVSS 8.1 high · EPSS 0.6% · published 2026-10-31
- CVE-2026-65183 — CVSS 8.1 high · EPSS 0.3% · published 2026-08-25
- CVE-2026-89430 — CVSS 8.1 high · EPSS 0.1% · published 2026-10-06
- CVE-2026-21523 — CVSS 8 high · EPSS 0.7% · published 2026-02-10
- CVE-2026-62428 — CVSS 7.8 high · EPSS 0.1% · published 2026-07-28
- CVE-2026-92374 — CVSS 7.8 high · EPSS 0.0% · published 2026-10-27
- CVE-2026-113865 — CVSS 7.8 high · published 2026-11-10
- CVE-2026-85045 — CVSS 7.5 high · EPSS 0.2% · published 2026-09-03
- CVE-2026-55391 — CVSS 7.5 high · published 2026-07-28
- CVE-2026-92369 — CVSS 7.3 high · EPSS 0.0% · published 2026-09-29
- CVE-2026-112791 — CVSS 7 high · EPSS 0.2% · published 2026-11-10
- CVE-2026-85920 — CVSS 7 high · EPSS 0.1% · published 2026-10-13
- CVE-2026-119398 — CVSS 7 high · published 2026-11-10
- CVE-2026-53410 — CVSS 7 high · published 2026-07-16
- CVE-2026-105481 — CVSS 6.5 medium · EPSS 0.3% · published 2026-10-23
- CVE-2026-13113 — CVSS 6.5 medium · EPSS 0.2% · published 2026-07-29
- CVE-2026-126906 — CVSS 5.9 medium · EPSS 0.1% · published 2026-11-11
- CVE-2026-105163 — CVSS 5.3 medium · EPSS 0.3% · published 2026-10-04
- CVE-2026-58041 — CVSS 5.3 medium · EPSS 0.2% · published 2026-08-04
- CVE-2026-13502 — CVSS 4.5 medium · EPSS 0.0% · published 2026-06-28
- CVE-2026-101029 — CVSS 4.3 medium · EPSS 0.1% · published 2026-10-06
- CVE-2026-48931 — CVSS 3.7 low · EPSS 0.3% · published 2026-06-22
- CVE-2026-126935 — CVSS 3.7 low · EPSS 0.3% · published 2026-11-11
- CVE-2026-93380 — CVSS 3.1 low · EPSS 0.2% · published 2026-09-17
- CVE-2026-87517 — CVSS 3.1 low · EPSS 0.1% · published 2026-09-09
- CVE-2026-43927 — EPSS 0.2% · published 2026-07-06
- CVE-2026-77059 — EPSS 0.1% · published 2026-10-26
- CVE-2026-109518 — published 2026-11-04
- CVE-2026-49036 — published 2026-11-10
Affected vendors
- Microsoft — 7 CVEs
- Google — 4 CVEs
- nodejs — 3 CVEs
- Gitea — 2 CVEs
- TeamViewer — 2 CVEs
- Apache Software Foundation — 1 CVE
- Debian — 1 CVE
- FOSSBilling — 1 CVE
- GitLab — 1 CVE
- N8n — 1 CVE
- Ubuntu — 1 CVE
- Vmware — 1 CVE
Threat activity
61 tracked threats cite CWE-367; the 25 most recent are listed.
- Google Chrome 157 Stable Update Fixes 83 Security Flaws Including 5 Critical Use-After-Free Bugs (CVE-2026-126885, CVE-2026-126895, CVE-2026-126879, CVE-2026-126846, CVE-2026-126911)CRITICAL
- Microsoft Patch Tuesday November 2026: ~1,095 vulnerabilities, 64 critical, one exploited Outlook NTLM-leak spoofing zero-day (CVE-2026-124194)CRITICAL
- Intel and AMD November 2026 Patch Tuesday: 200+ vulnerabilities incl. critical TDX MigTD flaws (CVE-2026-61887, CVE-2026-44685, CVE-2026-61473)CRITICAL
- Notepad++ 8.9.9 Fixes 6 Vulnerabilities (Local Privilege Escalation, Command Dispatch, Heap Overflows in MIME Tools) - No CVEs AssignedMEDIUM
- Microsoft November 2026 Patch Tuesday: Outlook Zero-Day CVE-2026-124194 Exploited to Steal NTLM Hashes (1,235 Flaws Fixed)HIGH
- Top 10 Critical Threat Actors to Watch in 2026: Akira, DragonForce, Qilin, LockBit, Scattered Spider, Cl0p, Lazarus, Volt Typhoon, APT29, OilRig (CVE-2024-40766, CVE-2025-61882, CVE-2023-34362, CVE-2024-39717, CVE-2024-30088)HIGH
- Debian and Ubuntu APT Flaw (CVE-2026-109518) Lets MitM Attackers Swap Verified Packages and Run Code as RootHIGH
- TeamViewer Integer Overflow (CVE-2026-111585) Lets Malicious Hosts Compromise Support Technicians' Viewer MachinesHIGH
- Active Exploitation of WordPress Core Unauthenticated Upgrade-Window RCE (Versions 4.7 through 7.1.3) Hours After 7.1.4 Patch ReleaseCRITICAL
- TeamViewer Remote Desktop Session Vulnerabilities (CVE-2026-92372, CVE-2026-111585, CVE-2026-92374) Enable Code ExecutionHIGH
- Tailscale 'Tailworm' Vulnerabilities (11 Findings in Tailscale SSH, App Connectors, Serve, DERP and Headscale) Allowing Root Privilege Escalation (Tailscale v1.104.2, Headscale v0.29.5)HIGH
- Multiple vulnerabilities in boneIO Black and black_debian_images, including unauthenticated Node-RED RCE (CVE-2026-77052 through CVE-2026-77062)HIGH
- BlueHammer (CVE-2026-33825) - Windows Defender Local Privilege Escalation, Exploited In The Wild and Added to CISA KEVHIGH
- Node.js October 2026 Security Releases Fix 10 Vulnerabilities Including Brotli Decoder RCE and TLS Hostname Verification Bypasses (CVE-2026-111497, CVE-2026-105483, CVE-2026-106069, CVE-2026-105482)CRITICAL
- Q2 2026 Vulnerability and Exploit Landscape: Exploited AI-platform flaws (OpenClaw CVE-2026-25253, Dify CVE-2026-41948, Open WebUI CVE-2026-45386), Exchange CVE-2026-45501, and Linux kernel page-cache LPE exploit wave (Copy Fail, Dirty Frag)HIGH
- OpenBSD Kernel 'Big Fish' shm_nattch Integer Overflow and ip_moptions Out-of-Bounds Write Chain Enables Local Privilege Escalation to Root (Public PoC)HIGH
- PwnEscape (CVE-2026-99999): Linux Kernel IPv4 Checksum-Offload Flaw Lets Guest VMs Read Host MemoryCRITICAL
- Windows BitLocker Vulnerabilities: Security Feature Bypass and Privilege Elevation (CVE-2026-85920, CVE-2026-88070, CVE-2026-83500)HIGH
- Full-chain Chrome exploit (V8 Maglev, WebP CVE-2026-85045, Crashpad CVE-2026-78952) built with GPT-5.6 Sol by XBOW earns $250,000 Google bountyHIGH
- Discourse Image Pipeline Exploit Chains JPEG Race, GhostScript and ImageMagick for Arbitrary File Read (CVE-2026-55420)HIGH
- Gitea 28.x Patches 27 Security Flaws Including Critical SSH Public-Key Authentication Bypass (CVE-2026-103059), SSRF/DNS Rebinding and Actions Approval BypassesCRITICAL
- Multiple Vulnerabilities in Microsoft Edge prior to 154.0.4258.53 (HK GovCERT A26-10-03)CRITICAL
- Multiple High-Severity Vulnerabilities in TeamViewer Client (CVE-2026-92370, CVE-2026-92368, CVE-2026-92369, CVE-2026-92371, CVE-2026-19743)HIGH
- Docker CopyEscape (CVE-2026-17106): docker cp / sbx cp flaw lets malicious containers overwrite host filesHIGH
- FalconFlank — CrowdStrike Falcon Sensor Local Privilege Escalation Zero-Day with Public PoCHIGH
Mitigations
- 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.
- Architecture and Design: Ensure that some environmental locking mechanism can be used to protect resources effectively.
- Implementation: Ensure that locking occurs before the check, as opposed to afterwards, such that the resource, as checked, is the same as it is when in use.
Source: MITRE CWE, potential mitigations.
Detection methods (MITRE CWE)
- Automated Static Analysis (effectiveness: High): Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.