Vulnerability · CVE-2026-35367
The nohup utility in uutils coreutils creates its default output file, nohup.out, without specifying explicit restricted permissions.
Published Apr 22, 2026 · catalog updated Jun 17, 2026 · The nohup utility in
Check if you run it
No confirmed exploitation is on record for CVE-2026-35367. EPSS is 0.13%. Act only if a listed version of The nohup utility in is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (The nohup utility in).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Low3.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.13%
- Remediation
- Not established
- Affected products
- cpe uutils/coreutils
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe uutils/coreutilsversion unspecified
How to fix CVE-2026-35367
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-35367. EPSS is 0.13%. Act only if a listed version of The nohup utility in is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-732: Incorrect Permission Assignment for Critical Resource. EPSS 0.13%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
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.
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
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
Sources
- CVE.orgVulnerability recordCVE-2026-35367
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-35367
30-day exploitation probability 0.1%
first.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
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.