Uutils coreutils Split Utility toctou

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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Uutils

Name

• coreutils

Website

• Product: https://github.com/uutils/coreutils/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion