CVE-2026-35377 | uutils coreutils env Local Denial of Service via Improper Handling of Backslashes in Split-String Mode

A logic error in the env utility of uutils coreutils causes a failure to correctly parse command-line arguments when utilizing the -S (split-string) option. In GNU env, backslashes within single quotes are treated literally (with the exceptions of \\ and \'). However, the uutils implementation incorrectly attempts to validate these sequences, resulting in an "invalid sequence" error and an immediate process termination with an exit status of 125 when encountering valid but unrecognized sequences like \a or \x. This divergence from GNU behavior breaks compatibility for automated scripts and administrative workflows that rely on standard split-string semantics, leading to a local denial of service for those operations.

Published: 2026-04-22 Last update: 2026-04-24 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-35377 is rated Low Risk (14.2/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). Mandatory action: Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-35377

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-23 0.01%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-35377

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
1.8 1.4 [email protected]

Weakness enumeration for CVE-2026-35377

GitHub Security Advisory for CVE-2026-35377

GHSA-5v4g-vw9x-h534 · Severity: low · Ecosystem: rust — uutils coreutils has an Improper Input Validation Issue in its env Utility

OS Trackers for CVE-2026-35377

vendor priority summary link
debian not yet assigned CVE-2026-35377 not yet assigned priority: Debian including 1 source packages (rust-coreutils), 3 status rows across 3 suites (bookworm, sid, trixie): open 3. https://security-tracker.debian.org/tracker/CVE-2026-35377
ubuntu medium CVE-2026-35377 medium priority: Ubuntu including 1 source packages (rust-coreutils), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): needed 4, DNE 1. https://ubuntu.com/security/CVE-2026-35377

Affected software / configurations for CVE-2026-35377

Vendor Product Version Raw CPE
uutils coreutils cpe:2.3:a:uutils:coreutils:-:*:*:*:*:rust:*:*

References for CVE-2026-35377

cvelogic Threat Intelligence