Uutils coreutils up to 0.5.x comm Utility String::from_utf8_lossy unicode encoding

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Uutils coreutils up to 0.5.x. This issue affects the function String::from_utf8_lossy of the component comm Utility. Performing a manipulation results in improper handling of unicode encoding. This vulnerability is cataloged as CVE-2026-35346. The attack must be initiated from a local position. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Uutils coreutils up to 0.5.x. It has been classified as problematic. This affects the function String::from_utf8_lossy of the component comm Utility. The manipulation with an unknown input leads to a improper handling of unicode encoding vulnerability. CWE is classifying the issue as CWE-176. The product does not properly handle when an input contains Unicode encoding. This is going to have an impact on integrity. The summary by CVE is:

The comm utility in uutils coreutils silently corrupts data by performing lossy UTF-8 conversion on all output lines. The implementation uses String::from_utf8_lossy(), which replaces invalid UTF-8 byte sequences with the Unicode replacement character (U+FFFD). This behavior differs from GNU comm, which processes raw bytes and preserves the original input. This results in corrupted output when the utility is used to compare binary files or files using non-UTF-8 legacy encodings.

The weakness was shared by Zellic. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-35346 since 04/02/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 309850 (Linux Distros Unpatched Vulnerability : CVE-2026-35346), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 0.6.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (309850). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Uutils

Name

• coreutils

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5

Website

• Product: https://github.com/uutils/coreutils/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion