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

Exp

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.

Published: 2026-04-22 Last update: 2026-05-04 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-35375 is rated Exploit Available (50/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-35375

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-35375

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-23 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-35375

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 [email protected]

Weakness enumeration for CVE-2026-35375

GitHub Security Advisory for CVE-2026-35375

GHSA-vx9m-xjwf-8cqm · Severity: low · Ecosystem: rust — uutils coreutils has an Improper Handling of Unicode Encoding Issue

OS Trackers for CVE-2026-35375

vendor priority summary link
debian not yet assigned CVE-2026-35375 not yet assigned priority: Debian including 1 source packages (rust-coreutils), 3 status rows across 3 suites (bookworm, sid, trixie): open 2, resolved 1. https://security-tracker.debian.org/tracker/CVE-2026-35375
ubuntu medium CVE-2026-35375 medium priority: Ubuntu including 1 source packages (rust-coreutils), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): needed 2, DNE 1, not-affected 1, released 1. https://ubuntu.com/security/CVE-2026-35375

Affected software / configurations for CVE-2026-35375

Vendor Product Version Raw CPE
uutils coreutils < 0.8.0 cpe:2.3:a:uutils:coreutils:*:*:*:*:*:rust:*:*

References for CVE-2026-35375

cvelogic Threat Intelligence