Cyber Resilience

CVE-2026-35375

Uutils Coreutils ≤ 0.8.0

Public PoC
Published
22 April 2026
Modified
04 May 2026
Patch / advisory
View advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0014 4th percentile
Risk Priority 27 floored blend · peak EPSS

Summary

CVE-2026-35375 is a low-severity Improper Handling of Unicode Encoding (CWE-176) vulnerability in Uutils Coreutils. Its CVSS base score is 3.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Invisible Unicode (T1027.018); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-176

Related Threats

MITRE ATT&CK Enterprise Techniques

T1027.018 Invisible Unicode Stealth
Adversaries may abuse invisible or non-printing Unicode characters to conceal malicious content within files, scripts, or text.
attack.mitre.org →
T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
attack.mitre.org →
T1132 Data Encoding Command And Control
Adversaries may encode data to make the content of command and control traffic more difficult to detect.
attack.mitre.org →
T1132.002 Non-Standard Encoding Command And Control
Adversaries may encode data with a non-standard data encoding system to make the content of command and control traffic more difficult to detect.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-35373Same product: Uutils Coreutils
CVE-2026-35346Same product: Uutils Coreutils
CVE-2026-35338Same product: Uutils Coreutils
CVE-2026-35363Same product: Uutils Coreutils
CVE-2026-35344Same product: Uutils Coreutils
CVE-2026-35380Same product: Uutils Coreutils
CVE-2026-35369Same product: Uutils Coreutils
CVE-2026-35377Same product: Uutils Coreutils
CVE-2026-35347Same product: Uutils Coreutils
CVE-2026-35370Same product: Uutils Coreutils

Affected Assets

uutils
coreutils
≤ 0.8.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly requires checking and normalizing encodings so that Unicode is handled consistently before further processing.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper Unicode/input validation to prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect Unicode-handling flaws before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and encoding handling that can prevent Unicode mishandling.

A.8.26 Application security requirements partial match
prevents

Application security requirements include proper handling of character encodings and input sanitization.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require robust input processing to avoid encoding-related vulnerabilities.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly address proper Unicode and character-encoding validation.

References