The nohup utility in uutils coreutils creates its default output file, nohup.out, without specifying explicit restricted permissions.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. Apr 22, 2026 · NIST NVD

   Detected

   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 inform

2. Jun 17, 2026 · NIST NVD

   Updated

   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 inform

Affected

• cpe uutils/coreutilsversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-35367

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-35367

  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 all

  nvd.nist.gov

References

• Exploit · github.com