CVE-2026-35375

uutils coreutils split Local Data Integrity Issue via Lossy Filename Encoding

Published Apr 22, 2026 CVSS 3.1 · 3.3 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A logic error in the split utility of uutils coreutils causes corruption of output filenames when non‑UTF‑8 prefixes or suffixes are supplied. The code uses to_string_lossy(), converting invalid byte sequences into the Unicode replacement character U+FFFD, which differs from GNU split that preserves raw bytes. This results in files being written with incorrect names, potentially leading to filename collisions, broken scripts, or misdirected output data.

Affected Systems

The uutils coreutils split command is affected. No explicit affected–version information is provided; however, the vulnerability was fixed in the 0.8.0 release as indicated by the advisory links.

Risk and Exploitability

The CVSS score is 3.3, indicating a low severity. The EPSS score is unavailable, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the attack vector is local and that an attacker would need write access to the directory where split is executed. Exploitation would result only in data integrity problems rather than broader system compromise.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade uutils coreutils to version 0.8.0 or later to apply the authoritative fix.
  • Until the update is applied, avoid using split with non‑UTF‑8 prefixes or suffixes; ensure that all inputs to split are valid UTF‑8 to prevent lossy filename encoding.
  • Implement validation of filename characters in scripts that call split to detect and correct invalid names before processing the output.

Generated by OpenCVE AI on April 27, 2026 at 08:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-vx9m-xjwf-8cqm uutils coreutils has an Improper Handling of Unicode Encoding Issue
History
Type Values Removed Values Added
CPEs cpe:2.3:a:uutils:coreutils:*:*:*:*:*:rust:*:*
Type Values Removed Values Added
First Time appeared Uutils
Uutils coreutils
Vendors & Products Uutils
Uutils coreutils
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title uutils coreutils split Local Data Integrity Issue via Lossy Filename Encoding
Weaknesses CWE-176
References
Metrics cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-176

    Improper Handling of Unicode Encoding

Sources

Status
PUBLISHED
Assigner
canonical
Published
Updated
Apr 22, 2026, 5:17 PM
Reserved
Apr 2, 2026, 12:58 PM
Status
Analyzed
Published
Apr 22, 2026, 5:16 PM
Modified
Oct 26, 2026, 10:10 PM