CVE-2026-35347: Stream-draining and hang flaw in uutils coreutils comm
- Vendor
- Uutils
The comm utility in uutils coreutils improperly reads from both input paths in are_files_identical before verifying that the inputs are regular files. As described, this pre-comparison content check opens and consumes data from the supplied paths even when they refer to non-regular file inputs such as FIFOs or pipes. When such streamed inputs are used, the pre-read drains the stream before the actual comparison logic executes, causing silent loss of input data and incorrect results. If the utility performs this pre-read against an infinite stream such as /dev/zero, it may block indefinitely.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful triggering of this flaw causes incorrect and unsafe behavior rather than memory corruption. For FIFO or pipe inputs, data can be silently consumed before comm performs its intended comparison, resulting in data loss, corrupted processing semantics, and unreliable output. For infinite or unbounded streams, the utility may hang indefinitely, creating a denial-of-service condition for the invoking process or any workflow that depends on it.
Mitigation
If you can’t patch tonight, do this now.
Avoid using the affected comm implementation with non-regular file inputs such as FIFOs, named pipes, or other streaming sources until patched. Prefer regular files as inputs, and avoid passing infinite streams such as /dev/zero. Where possible, use the GNU coreutils comm implementation or another known-good alternative until the fixed uutils version is deployed.
Remediation
Patch, then assume compromise.
Upgrade to uu_comm 0.6.0 or later, which fixes the improper pre-read behavior on non-regular file inputs. If a broader uutils coreutils package update is available from the vendor or distribution that includes this fix, apply that update.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-35347 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2026-35347 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-35347?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2026-35347.
- Is there a patch for CVE-2026-35347?
- Upgrade to uu_comm 0.6.0 or later, which fixes the improper pre-read behavior on non-regular file inputs. If a broader uutils coreutils package update is available from the vendor or distribution that includes this fix, apply that update.
- What products are affected by CVE-2026-35347?
- Uutils Coreutils.
- How severe is CVE-2026-35347?
- CVE-2026-35347 has a CVSS v3.1 score of 4.4 (Medium) and an EPSS score of 0.14% (3rd percentile) as of Oct 16, 2026.
Recent activity
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.