CVE-2026-35375 uutils coreutils split Local Data Integrity Issue via Lossy Filename Encoding

Low 3.3 Published Updated

Attackers can corrupt output filenames in split utility via non-UTF-8 inputs, causing data misdirection or collisions in non-UTF-8 environments.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-35375?

CVE-2026-35375 is a low-severity vulnerability in Uutils coreutils, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

A logic error in the split utility of uutils coreutils causes the corruption of output filenames when provided with non-UTF-8 prefix or suffix inputs. The implementation utilizes to_string_lossy() when constructing chunk filenames, which automatically rewrites invalid byte sequences into the UTF-8 replacement character (U+FFFD). This behavior diverges from GNU split, which preserves raw pathname bytes intact. In environments utilizing non-UTF-8 encodings, this vulnerability leads to the creation of files with incorrect names, potentially causing filename collisions, broken automation, or the misdirection of output data.

Weakness: CWE-176

Which versions are affected by CVE-2026-35375?

2 open source packages ship an affected version, including coreutils. It affects 1 product.

PackageAffectedFixed in
coreutils crates.ioAll versions0.8.0
coreutils crates.ioAll versions0.8.0

Products include Uutils Coreutils.

How do I fix CVE-2026-35375?

Upgrade coreutils to 0.8.0 or later.

Is CVE-2026-35375 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35375 exists.

Sources

Also known as DEBIAN-CVE-2026-35375, GHSA-vx9m-xjwf-8cqm, UBUNTU-CVE-2026-35375.

Is CVE-2026-35375 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free