CVE-2026-35358
Uutils Coreutils ≤ 0.7.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LSummary
CVE-2026-35358 is a medium-severity Use of Incorrectly-Resolved Name or Reference (CWE-706) vulnerability in Uutils Coreutils. Its CVSS base score is 4.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and AC-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-24998
Vulnerability Data
The cp utility in uutils coreutils, when performing recursive copies (-R), incorrectly treats character and block device nodes as stream sources rather than preserving them. Because the implementation reads bytes into regular files at the destination instead of using mknod,…
more
device semantics are destroyed (e.g., /dev/null becomes a regular file). This behavior can lead to runtime denial of service through disk exhaustion or process hangs when reading from unbounded device nodes.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability in cp utility enables disk exhaustion or process hangs via mishandled device nodes, directly facilitating endpoint DoS.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires patching the flawed cp implementation in uutils coreutils so that device nodes are preserved via mknod rather than read as byte streams.
Requires integrity verification of critical device files so that replacement of /dev nodes by regular files created during a faulty recursive copy is detected.
Enforces least privilege so that only authorized processes may perform recursive copies over directories containing device special files, limiting exposure to the mishandling bug.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly prevent incorrect name/reference resolution bugs during coding.
Enforced authorization boundaries limit damage from an incorrectly resolved reference.
Logical segmentation and access controls reduce the chance an out-of-sphere resolution succeeds.
Hardened configuration baselines can constrain allowable name-to-resource mappings.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect incorrect name or reference resolution through fuzzing and negative test cases.
Network segmentation and routing policies reduce the chance that a mis-resolved name leads to an unintended external resource.
Segregated networks limit the blast radius when a name or reference resolves outside the intended control sphere.
Secure SDLC practices include design reviews that can catch incorrect name or reference handling before deployment.
Application security requirements can mandate validation of all external references and names used at runtime.
Secure architecture principles discourage reliance on ambient or globally-resolvable names without explicit scoping.