CVE-2026-35367 json
uutils coreutils nohup Information Disclosure via Insecure Default Output Permissions
published 6mo ago modified 14d ago also GHSA-5hgf-628x-mcqf , EUVD-2026-25015
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- rust-coreutils Debian 14 0.9.0-1
debian advisories DEBIAN-CVE-2026-35367
Is CVE-2026-35367 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-35367 updated cvss 3.3
rust-coreutils: nohup: information disclosure via insecure default output permissions
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/uutils/coreutils/issues/10021 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | coreutils | <=0.8.0 |
no fix listed |
Affected products
- Uutils coreutils
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
github.com
/uutils/coreutils/issues/10021
issue-tracking, exploit, web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-35367
advisory
-
github.com
/uutils/coreutils
package
Sources
- CVE List CVE-2026-35367
- GitHub Advisory GHSA-5hgf-628x-mcqf
- NVD CVE-2026-35367
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.