Skip to main content
VulnerabilityPublished

CVE-2026-35375: Uutils coreutils · Improper Handling of Unicode Encoding

Affects Uutils coreutilsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.3 Low : upgrade to 0.8.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.8.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Uutils coreutils to 0.8.0.

Affected software

ProductAffectedFixed in
UutilscoreutilsAffected
  • <0.8.0
Fixed in
  • 0.8.0
GitHubuutils/coreutilspkg:github/uutils/coreutilsOther threatsAffected
  • =0
Fixed in–
GitHubcoreutilspkg:github/coreutilsOther threatsAffected
  • <0.8.0
Fixed in
  • 0.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should be cautious when using the split utility with non-UTF-8 encoded prefixes or suffixes and consider using GNU split as an alternative if filename integrity is critical.

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.

References

Community reviews

Loading reviews…