CVE-2026-35367

uutils coreutils nohup Information Disclosure via Insecure Default Output Permissions

Published Apr 22, 2026 CVSS 3.1 · 3.3 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

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 0644. As a result any user on a multi‑user system can read the stdout/stderr captured by nohup, potentially exposing sensitive data. This divergence from the behavior of GNU coreutils, which restricts nohup.out to 0600, represents an information disclosure flaw classified as CWE‑732.

Affected Systems

The flaw affects the uutils coreutils package, specifically the nohup component. No particular versions were listed, so any installation of this package that relies on the default nohup behavior is vulnerable. The impact is relevant in any environment where multiple users share a system and use nohup to run commands that produce output.

Risk and Exploitability

The CVSS score of 3.3 indicates a low severity vulnerability, and the EPSS score is not available, suggesting limited evidence of attack activity. The vulnerability is not listed in CISA KEV, further supporting a low exploitation likelihood. The attack vector is local; any user with the ability to run a command under nohup could read the generated nohup.out file and recover whatever data was written to stdout or stderr.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the uutils coreutils package to a version that sets explicit 0600 permissions on nohup.out.
  • If an update is not possible, redirect nohup output to a file created with restrictive permissions or to /dev/null, e.g., `nohup command > myoutput.log 2>&1 &` and then change the permissions of `myoutput.log` immediately.
  • Use the GNU coreutils implementation of nohup, which creates the output file with owner‑only permissions, or wrap the `nohup` call in a script that sets `umask 077` before execution.

Generated by OpenCVE AI on April 27, 2026 at 08:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-5hgf-628x-mcqf uutils coreutils has an Incorrect Permission Assignment for Critical Resource
Ubuntu USN Ubuntu USN USN-9041-1 uutils coreutils vulnerabilities
History
Type Values Removed Values Added
First Time appeared Uutils
Uutils coreutils
CPEs cpe:2.3:a:uutils:coreutils:-:*:*:*:*:rust:*:*
Vendors & Products Uutils
Uutils coreutils
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

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

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses
  • CWE-732

    Incorrect Permission Assignment for Critical Resource

Sources

Status
PUBLISHED
Assigner
canonical
Published
Updated
Apr 22, 2026, 5:49 PM
Reserved
Apr 2, 2026, 12:58 PM
Status
Analyzed
Published
Apr 22, 2026, 5:16 PM
Modified
Oct 26, 2026, 10:10 PM