CVE-2026-35367 | uutils coreutils nohup Information Disclosure via Insecure Default Output Permissions

Exp

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.

Published: 2026-04-22 Last update: 2026-04-24 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-35367 is rated Exploit Available (50/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.11%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2026-35367

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2026-35367

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.11% +0.10%
2 2026-04-23 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-35367

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 1.4 [email protected]

Weakness enumeration for CVE-2026-35367

GitHub Security Advisory for CVE-2026-35367

GHSA-5hgf-628x-mcqf · Severity: low · Ecosystem: rust — uutils coreutils has an Incorrect Permission Assignment for Critical Resource

OS Trackers for CVE-2026-35367

vendor priority summary link
debian not yet assigned CVE-2026-35367 not yet assigned priority: Debian including 1 source packages (rust-coreutils), 4 status rows across 4 suites (bookworm, forky, sid, trixie): open 2, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-35367
ubuntu medium CVE-2026-35367 medium priority: Ubuntu including 1 source packages (rust-coreutils), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): needed 4, DNE 1. https://ubuntu.com/security/CVE-2026-35367

Affected software / configurations for CVE-2026-35367

Vendor Product Version Raw CPE
uutils coreutils — cpe:2.3:a:uutils:coreutils:-:*:*:*:*:rust:*:*

References for CVE-2026-35367

URL Tags
https://github.com/uutils/coreutils/issues/10021 Exploit Issue Tracking Vendor Advisory
cvelogic Threat Intelligence