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.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://github.com/uutils/coreutils/issues/10021 |
|
History
Wed, 22 Apr 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 22 Apr 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | uutils coreutils nohup Information Disclosure via Insecure Default Output Permissions | |
| Weaknesses | CWE-732 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: canonical
Published:
Updated: 2026-04-22T17:49:29.072Z
Reserved: 2026-04-02T12:58:56.088Z
Link: CVE-2026-35367
Updated: 2026-04-22T17:49:19.375Z
Status : Awaiting Analysis
Published: 2026-04-22T17:16:40.423
Modified: 2026-04-22T21:23:52.620
Link: CVE-2026-35367
No data.
OpenCVE Enrichment
Updated: 2026-04-22T18:15:15Z