Skip to main content
VulnerabilityPublished Updated

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

Affects coreutilsSource GCVE Database

0
Authoritative record:CVE-2026-35375· Low 3.3

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

Data as of 27 Oct 2026, 00:27 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
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. Weaponised: 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 26 Oct 2026.

What to do

Upgrade coreutils to 0.8.0.

Affected software

ProductAffectedFixed in
crates.iocoreutilsAffected
  • <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

A patch is available in uutils coreutils version 0.8.0 that fixes this issue. Users should upgrade to version 0.8.0 or later to resolve the improper Unicode handling in the split utility. No additional mitigation is required.

Description

A logic error in the split utility of uutils coreutils causes output filename corruption when non-UTF-8 prefix or suffix inputs are used. The utility uses to_string_lossy(), which replaces invalid byte sequences with the UTF-8 replacement character, unlike GNU split which preserves raw bytes. This can lead to incorrect filenames, causing filename collisions, broken automation, or misdirected output data in non-UTF-8 environments. The issue affects versions before 0.8.0 and has a low severity rating. A fix is available in version 0.8.0.

References

Community reviews

Loading reviews…