Uutils coreutils sort panic on non-UTF-8 filenames causes local denial of service

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-35348?

CVE-2026-35348 is a vulnerability classified as Uncaught Exception, affecting coreutils. This vulnerability is rated Medium, with a CVSS score of 5.5. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

The sort utility in uutils coreutils is vulnerable to a process panic when using the --files0-from option with inputs containing non-UTF-8 filenames. The implementation enforces UTF-8 encoding and utilizes expect(), causing an immediate crash when encountering valid but non-UTF-8 paths. This diverges from GNU sort, which treats filenames as raw bytes. A local attacker can exploit this to crash the utility and disrupt automated pipelines.

Affected products and scope

  • Uutils coreutils: the consulted advisory identifies versions <= 0.8.0 as affected and lists no patched version.
  • The CNA marks the product affected by default on Linux, Unix, and macOS.
  • The upstream issue was later closed as completed after a source-level change intended to handle raw-byte filenames, but the available evidence does not map that change to a specific released version. Do not assume that later or parallel package branches are fixed without confirmation from the package maintainer.

Technical details

The affected component is the sort utility when it processes NUL-separated filenames through --files0-from. The vulnerable implementation decodes each filename as UTF-8 and then uses expect(). A valid filename containing non-UTF-8 bytes therefore triggers an uncaught exception and process panic instead of being handled as a raw-byte path. Reaching the fault requires local ability to run the utility with a --files0-from input that contains such a filename; the record describes local reachability, low complexity, low privileges, and no user interaction. CNA data identifies Linux, Unix, and macOS deployments as affected, while details for every downstream package or build variant remain unconfirmed.

Exploitability

Exploitation is local. The record describes low attack complexity, low privileges, and no user interaction, but an attacker still needs a vulnerable sort invocation using --files0-from and an input containing a non-UTF-8 filename. The supplied record marks a public exploit, and the GCVE enrichment classifies exploitation as a PoC. The available evidence does not establish active exploitation in the wild. The direct result is termination of the sort process and possible denial of service to the affected utility or pipeline.

Technical impact

The direct technical outcome is a panic and early termination of sort when a non-UTF-8 filename is encountered in --files0-from data. In an automated pipeline, this can fail the step, produce incomplete output, or prevent downstream stages from continuing. The supplied impact data limits the effect to process availability and does not identify data disclosure, data modification, privilege escalation, or a security-scope crossing. Organisational impact depends on whether the pipeline retries failed jobs, checks exit status, and validates output completeness.

Business impact

Organizations using Uutils coreutils in CI/CD, build, backup, ETL, or file-processing pipelines may be affected when a workflow invokes sort --files0-from with a list containing a non-UTF-8 filename. A locally created or controlled input can cause the sort step to fail, omit output, or prevent downstream stages from running. Depending on pipeline design, this can lead to retries, processing delays, missing artifacts, or incomplete output. These are possible operational consequences, not evidence of a breach or confirmed data modification.

Remediation

  1. Inventory all Uutils coreutils installations and the package versions actually deployed. Treat versions <= 0.8.0 as affected, and do not infer that a newer branch is fixed merely because the upstream issue was closed.
  2. Upgrade to a vendor or package-maintainer release that explicitly includes the corrective change. The consulted advisory lists no patched release, so verify the package release notes or source contents before closing the finding.
  3. Until a verified fix is deployed, avoid the vulnerable sort --files0-from path for filename sets that may contain non-UTF-8 bytes. Where operationally acceptable, use GNU sort for this workload because the issue evidence identifies its raw-byte filename handling as the compatible behavior.
  4. Add a regression test with NUL-separated input containing a valid non-UTF-8 filename, and confirm that the job exits normally and produces the expected result.

Detection

  1. Inventory Uutils coreutils installations on Linux, Unix, and macOS, recording the package and binary versions actually used by automated jobs.
  2. Review scripts, CI/CD jobs, and file-processing workflows for sort invocations using --files0-from, especially when NUL-separated lists can contain filenames from untrusted or arbitrary sources.
  3. In a staging environment, test a representative workload containing a filename with non-UTF-8 bytes and verify that the process completes normally instead of panicking.
  4. Review stderr and job logs for abrupt sort termination or panic messages associated with Utf8Error. Treat these as precautionary signals rather than unique indicators; absence of the messages does not prove that the system is safe.
Sources (23)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.