Description
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.
Affected products
uutils: coreutils
References2
- github.com/uutils/coreutils/issues/10021 ExploitIssue TrackingVendor Advisory
- github.com/uutils/coreutils/issues/10021 ExploitIssue TrackingVendor Advisory
Metrics
- CVSS 3.1
-
3.3
LOW
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - EPSS — exploit probability
- 0% percentile: 2 · as of 13 November 2026
- CWE
- CWE-732
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.