CVE-2026-35367
MediumSummary
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).
Risk Assessment
In multi-user environments, any user can read the nohup.out file, potentially leaking sensitive data written by the process launched with nohup.
Recommendation
Update uutils coreutils to a version where nohup explicitly sets restrictive permissions (e.g., 0600) for nohup.out. Until then, manually set appropriate permissions after running nohup.
Original NVD description (English source)
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