CVE-2026-35367: uutils coreutils has an Incorrect Permission Assignment for Critical Resource

CVE-2026-35367 · Severity: low · CVSS 3.3 · Published 2026-04-22

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.

Technologies: coreutils (crates.io), Uutils Coreutils. Vendors: crates.io, Uutils.

Quick answers

Is CVE-2026-35367 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-35367 being exploited in the wild.
How severe is CVE-2026-35367?
Low severity, with a CVSS score of 3.3, published 22 April 2026.
Which products and versions are affected?
coreutils (crates.io) SEMVER:introduced=0,last_affected=0.8.0.
Is there a fix for CVE-2026-35367?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-35367?
Check whether you run coreutils (crates.io) or Uutils Coreutils at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • coreutils (crates.io) SEMVER:introduced=0,last_affected=0.8.0
  • Uutils Coreutils

Identifiers

  • CVE-2026-35367
  • GHSA-5hgf-628x-mcqf

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.