CVE-2026-35375 json
uutils coreutils split Local Data Integrity Issue via Lossy Filename Encoding
published 6mo ago modified 14d ago also GHSA-vx9m-xjwf-8cqm , EUVD-2026-25026
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io coreutils 0.8.0
- Uutils coreutils 0.8.0
- rust-coreutils Debian 14 0.8.0-1
debian advisories DEBIAN-CVE-2026-35375
- github.com/uutils/coreutils@d2b9550 commit
- github.com/uutils/coreutils#11397 pull request
- github.com/uutils/coreutils/releases/tag/0.8.0 release
Is CVE-2026-35375 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-35375 updated cvss 3.3
rust-coreutils: split: local data integrity issue via lossy filename encoding
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/uutils/coreutils/pull/11397 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | coreutils | <0.8.0 |
0.8.0 |
Affected products
- Uutils coreutils
Classification
- Weakness
-
- CWE-176 Improper Handling of Unicode Encoding
References
-
github.com
/uutils/coreutils/pull/11397
issue-tracking, patch, web, exploit
-
github.com
/uutils/coreutils/commit/d2b9550fe821a9a10bf0cec057509211357363f1
web
-
github.com
/uutils/coreutils/releases/tag/0.8.0
vendor-advisory, web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-35375
advisory
-
github.com
/uutils/coreutils
package
Sources
- CVE List CVE-2026-35375
- GitHub Advisory GHSA-vx9m-xjwf-8cqm
- NVD CVE-2026-35375
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.