CVE-2026-35374 | Uutils coreutils Split Utility toctou

VDB-359037 · CVE-2026-35374 · GCVE-0-2026-35374 UUTILS COREUTILS SPLIT UTILITY TOCTOU HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.9 $0-$5k 3.25 Summaryinfo A vulnerability was found in Uutils coreutils. It has been rated as problematic. This affects an unknown function of the component Split Utility. Performing a manipulation results in toctou. This vulnerability is reported as CVE-2026-35374. The attack requires a local approach. No exploit exists. Detailsinfo A vulnerability classified as problematic has been found in Uutils coreutils (version unknown). This affects an unknown function of the component Split Utility. The manipulation with an unknown input leads to a toctou vulnerability. CWE is classifying the issue as 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. This can cause the product to perform invalid actions when the resource is in an unexpected state. This is going to have an impact on integrity, and availability. The summary by CVE is: A Time-of-Check to Time-of-Use (TOCTOU) vulnerability exists in the split utility of uutils coreutils. The program attempts to prevent data loss by checking for identity between input and output files using their file paths before initiating the split operation. However, the utility subsequently opens the output file with truncation after this path-based validation is complete. A local attacker with write access to the directory can exploit this race window by manipulating mutable path components (e.g., swapping a path with a symbolic link). This can cause split to truncate and write to an unintended target file, potentially including the input file itself or other sensitive files accessible to the process, leading to permanent data loss. The weakness was disclosed by Zellic. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-35374 since 04/02/2026. The exploitability is told to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Vendor Uutils Name coreutils Website Product: https://github.com/uutils/coreutils/ CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 4.9 VulDB Meta Temp Score: 4.9 VulDB Base Score: 3.6 VulDB Temp Score: 3.6 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 6.3 CNA Vector (canonical): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Toctou CWE: CWE-367 / CWE-362 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/02/2026 CVE reserved 04/22/2026 +20 days Advisory disclosed 04/22/2026 +0 days VulDB entry created 04/22/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Researcher: Zellic Status: Confirmed CVE: CVE-2026-35374 (🔒) GCVE (CVE): GCVE-0-2026-35374 GCVE (VulDB): GCVE-100-359037 Entryinfo Created: 04/22/2026 19:05 Changes: 04/22/2026 19:05 (61) Complete: 🔍 Cache ID: 99:171:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸