CVE-2026-35375: uutils coreutils split Local Data Integrity Issue via Lossy Filename Encoding
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 tostringlossy() 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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-35375?
CVE-2026-35375 is categorized as a local data integrity issue that can lead to filename corruption.
How do I fix CVE-2026-35375?
To fix CVE-2026-35375, update uutils coreutils to the latest version where the issue has been addressed.
What versions of uutils coreutils are affected by CVE-2026-35375?
CVE-2026-35375 affects versions prior to the fix implemented in uutils coreutils version 0.8.0.
What is the main issue caused by CVE-2026-35375?
The main issue caused by CVE-2026-35375 is the corruption of output filenames due to lossy encoding of non-UTF-8 characters.
Is there a workaround for CVE-2026-35375?
There are no known workarounds for CVE-2026-35375, the best solution is to update to the fixed version.