CVE-2026-35367: uutils coreutils has an Incorrect Permission Assignment for Critical Resource
Affects coreutilsSource GCVE Database
Not known to be exploited · CVSS 3.3 Low.
Data as of 27 Oct 2026, 00:27 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| crates.iocoreutils | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should consider manually restricting permissions on nohup.out files after creation or use alternative utilities that enforce stricter file permissions. Monitor vendor advisories for any forthcoming patches or official fixes.
Description
The nohup utility in uutils coreutils creates its default output file nohup.out with permissions that are not explicitly restricted, typically resulting in a world-readable file (0644). This can expose the stdout/stderr output of commands to other users on a multi-user system, potentially leaking sensitive information. This differs from GNU coreutils, which restricts nohup.out to owner-only permissions (0600).