UBUNTU-CVE-2026-35377 (CVE-2026-35377)
Vulnerability from osv_ubuntu – Published: 2026-04-22 17:16 – Updated: 2026-09-21 18:36 – Source websiteA 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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rust-coreutils",
"binary_version": "0.0.24-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "rust-coreutils",
"purl": "pkg:deb/ubuntu/rust-coreutils@0.0.24-2?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.0.20-1",
"0.0.22-1",
"0.0.23-1",
"0.0.23-2",
"0.0.23-3",
"0.0.24-1",
"0.0.24-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rust-coreutils",
"binary_version": "0.2.2-0ubuntu2.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "rust-coreutils",
"purl": "pkg:deb/ubuntu/rust-coreutils@0.2.2-0ubuntu2.1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.0.30-1",
"0.0.30-2",
"0.0.30-2ubuntu2",
"0.1.0-0ubuntu1",
"0.1.0+git20250711.2ba3a33-0ubuntu1",
"0.1.0+git20250711.2ba3a33-0ubuntu2",
"0.1.0+git20250711.2ba3a33-0ubuntu3",
"0.1.0+git20250711.2ba3a33-0ubuntu4",
"0.1.0+git20250801.cf79675-0ubuntu1",
"0.1.0+git20250813.4af2a84-0ubuntu2",
"0.1.0+git20250813.4af2a84-0ubuntu4",
"0.1.0+git20250813.4af2a84-0ubuntu6",
"0.1.0+git20250813.4af2a84-0ubuntu7",
"0.2.2-0ubuntu1",
"0.2.2-0ubuntu2",
"0.2.2-0ubuntu2.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "rust-coreutils",
"binary_version": "0.10.0-1ubuntu2~26.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "rust-coreutils",
"purl": "pkg:deb/ubuntu/rust-coreutils@0.10.0-1ubuntu2~26.04.1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.2.2-0ubuntu2",
"0.2.2-0ubuntu4",
"0.5.0-0ubuntu1",
"0.5.0-0ubuntu2",
"0.6.0-0ubuntu1",
"0.7.0-0ubuntu1",
"0.8.0-0ubuntu3",
"0.10.0-1ubuntu2~26.04.1"
]
}
],
"aliases": [],
"details": "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 \\\u0027). 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.",
"id": "UBUNTU-CVE-2026-35377",
"modified": "2026-09-21T18:36:50Z",
"published": "2026-04-22T17:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-35377"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35377"
},
{
"type": "REPORT",
"url": "https://github.com/uutils/coreutils/pull/11512"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-35377"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.