Skip to content
Sign in
CVE-2026-353753.3LowCWE-176

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

Uutils · coreutils

Vendor fix available · Affected: Uutils coreutils · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.1%probability of exploitation in the next 30 days
3rd percentile
050100

Higher than 3% of scored CVEs

3.3LowCVSS 3.1
Low

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • Uutils · coreutilsbefore 0.8.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
Uutils
Published
April 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-35375 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in