CVE-2026-35377: Local Denial of Service via Improper Single-Quote Backslash Parsing in uutils coreutils env

Vulnerability ID: CVE-2026-35377
CVSS Score: 3.3
Published: 2026-11-20

CVE-2026-35377 is an improper input validation vulnerability (CWE-20) in the env utility of uutils coreutils, the Rust-based reimplementation of GNU coreutils. When processing command-line arguments with the -S (--split-string) option, the uutils split-string tokenizer erroneously validates backslash sequences enclosed within single quotes against a fixed table of known escape characters. Under standard GNU env behavior, backslashes inside single quotes are treated literally (except for \ and \'). Because uutils rejects unrecognized sequences such as \a, \x, or | with exit code 125, automated scripts, shebang invocations, and administrative workflows relying on POSIX/GNU compatibility fail to execute, resulting in a local denial of service.

TL;DR

A parsing logic flaw in the uutils coreutils env utility (-S / --split-string mode) causes the process to reject literal backslash sequences inside single quotes and exit with status 125, leading to a local denial of service for dependent scripts and workflows.

Technical Details

  • CVE ID: CVE-2026-35377
  • Weakness Class: CWE-20 (Improper Input Validation)
  • Affected Component: uutils coreutils env (src/uu/env/src/split_iterator.rs)
  • Attack Vector: Local (AV:L) via env -S / --split-string argument parsing
  • CVSS v3.1 Score: 3.3 Low (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)
  • EPSS Score: 0.11% (1.13th Percentile)
  • Security Impact: Local Denial of Service (Process termination with exit code 125)
  • CISA KEV Status: Not Listed

Affected Systems

  • uutils coreutils (uu_env utility)
  • coreutils (uu_env): prior to commit 9d7a0e849109c82262ac2d65324739aac690200f (Fixed in: 9d7a0e849109c82262ac2d65324739aac690200f)

Code Analysis

Commit: 9d7a0e8

env: keep backslashes literal in single quotes

@@ -279,15 +279,10 @@ impl<'a> SplitIterator<'a> { self.take_one()?; Ok(()) } - Some(c) if REPLACEMENTS.iter().any(|&x| x.0 == c) => { - // See GNU test-suite e11: In single quotes, \t remains as it is. - // Comparing with GNU behavior: \a is not accepted and issues an error. - // So apparently only known sequences are allowed, even though they are not expanded.... bug of GNU? + Some(_) => { self.push_char_to_word(BACKSLASH); - self.take_one()?; Ok(()) } - Some(c) => Err(self.make_invalid_sequence_backslash_xin_minus_s(c)), } } 

Mitigation Strategies

  • Upgrade uutils coreutils (specifically the uu_env component) to a version containing commit 9d7a0e849109c82262ac2d65324739aac690200f.
  • Modify affected scripts using env -S to double-escape literal backslashes (using \ instead of ) inside single quotes as a temporary compatibility workaround.
  • Replace env -S shebang invocations with standard POSIX shell wrapper scripts where multi-argument shebang splitting is required on unpatched systems.

Remediation Steps:

  1. Test current env binary susceptibility by running: env -S "printf '%s' '\x'" and checking for exit status 125.
  2. Pull the latest uutils/coreutils source tree or update the uu_env Cargo dependency to include commit 9d7a0e849109c82262ac2d65324739aac690200f.
  3. Recompile and deploy the updated env binary across affected hosts or container base images.
  4. Re-run the verification test suite (tests/by-util/test_env.rs) to confirm single-quoted unknown backslash sequences remain literal while double-quoted and unquoted sequences still enforce strict validation.

References

Read the full report for CVE-2026-35377 on our website for more details including interactive diagrams and full exploit analysis.