Uutils coreutils up to 0.7.x split Utility to_string_lossy unicode encoding
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Uutils coreutils up to 0.7.x and classified as problematic. The affected element is the function to_string_lossy of the component split Utility. The manipulation leads to improper handling of unicode encoding.
This vulnerability is documented as CVE-2026-35375. The attack needs to be performed locally. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability was found in Uutils coreutils up to 0.7.x. It has been rated as problematic. This issue affects the function to_string_lossy of the component split Utility. The manipulation with an unknown input leads to a improper handling of unicode encoding vulnerability. Using CWE to declare the problem leads to CWE-176. The product does not properly handle when an input contains Unicode encoding. Impacted is integrity. The summary by CVE is:
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.
The weakness was released by Zellic. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-35375 since 04/02/2026. The exploitation is known to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 0.8.0 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/uutils/coreutils/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.3
CNA Vector (canonical): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper handling of unicode encodingCWE: CWE-176 / CWE-172
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: coreutils 0.8.0
Timeline
04/02/2026 CVE reserved04/22/2026 Advisory disclosed
04/22/2026 VulDB entry created
04/22/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Researcher: Zellic
Status: Confirmed
CVE: CVE-2026-35375 (🔒)
GCVE (CVE): GCVE-0-2026-35375
GCVE (VulDB): GCVE-100-358991
Entry
Created: 04/22/2026 18:41Changes: 04/22/2026 18:41 (65)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.