The nohup utility in uutils coreutils creates its default output file, nohup.out, without specifying explicit restricted permissions. This causes the file to inherit umask-based permissions, typically resulting in a world-readable file (0644). In multi-user environments, this allows any user on the system to read the captured stdout/stderr output of a command, potentially exposing sensitive information. This behavior diverges from GNU coreutils, which creates nohup.out with owner-only (0600) permissions.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/uutils/coreutils/issues/10021 Exploit, Issue Tracking, Vendor Advisory
- https://github.com/uutils/coreutils/issues/10021 Exploit, Issue Tracking, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 3.3 · uutilsNVD modified 2026-10-26 22:10
Affected (CPE criteria) 1
cpe:2.3:a:uutils:coreutils:-:*:*:*:*:rust:*:*
References 2
- https://github.com/uutils/coreutils/issues/10021 Exploit, Issue Tracking, Vendor Advisory
- https://github.com/uutils/coreutils/issues/10021 Exploit, Issue Tracking, Vendor Advisory