CVE-2026-35375: uutils coreutils has an Improper Handling of Unicode Encoding Issue

CVE-2026-35375 · Severity: low · CVSS 3.3 · Published 2026-04-22

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.

Technologies: coreutils (crates.io), Uutils Coreutils. Vendors: crates.io, Uutils.

Quick answers

Is CVE-2026-35375 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-35375 being exploited in the wild.
How severe is CVE-2026-35375?
Low severity, with a CVSS score of 3.3, published 22 April 2026.
Which products and versions are affected?
coreutils (crates.io) SEMVER:introduced=0,fixed=0.8.0.
Is there a fix for CVE-2026-35375?
Yes. coreutils (crates.io): upgrade to 0.8.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-35375?
Check whether you run coreutils (crates.io) or Uutils Coreutils at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • coreutils (crates.io): upgrade to 0.8.0 or later
    cargo update -p coreutils

Affected products

  • coreutils (crates.io) SEMVER:introduced=0,fixed=0.8.0
  • Uutils Coreutils

Identifiers

  • CVE-2026-35375
  • GHSA-vx9m-xjwf-8cqm

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.