CVE-2026-35374: split: TOCTOU output-open allows truncating a swapped file

Medium CVSS 6.3

OSV id
GHSA-fjjq-8hw5-cf9f
Also known as
CVE-2026-35374
Published
Last modified

Affected packages

PackageAffected versionsFixed in
uu_split
Cargo
< 0.10.0 0.10.0

How to fix it

Upgrade uu_split to 0.10.0 or later.

cargo update -p uu_split --precise 0.10.0
  • If it is an indirect dependency, `cargo update -p` still works; if a parent crate pins an older version, upgrade that crate.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

split checks input/output identity by path before opening the output, then opens with truncation, leaving a race window on mutable path components. GNU opens first and compares the opened output inode against the input before truncating. The race can cause split to truncate/write a file different from the one validated — including the input file or another file the process can access.

Fixed in 0.10.0 (PR #12565, commit 58040feb5c66fce588a7ffac299b3a23bd55cd81): the output open path is hardened against TOCTOU target swaps.


Zellic private finding (zellic-ext/coreutils-private PR #119). Reported in the Zellic uutils coreutils Program Security Assessment (for Canonical, Jan 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.