CVE-2026-35367: Insecure Default Output Permissions in uutils coreutils nohup
- Vendor
- Uutils
The nohup utility in uutils coreutils creates its default output file without explicitly restricting permissions to the owner. Permissions instead depend on the process umask, typically producing mode 0644 and allowing other local users to read captured standard output and standard error. With umask 000, the file can be created with mode 0666, permitting other users to modify it as well. GNU coreutils nohup instead creates the file with owner-only mode 0600. The vulnerable behavior was demonstrated in uutils coreutils 0.8.0 on Ubuntu 26.04.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Other local users can read sensitive information written to the default output file when its permissions and containing-directory permissions allow access. Under a sufficiently permissive umask, such as 000, other users can also modify or truncate the captured output, compromising its integrity. Exposure depends on the information emitted by the executed command.
Mitigation
If you can’t patch tonight, do this now.
Use GNU coreutils nohup instead of the affected uutils implementation, or set umask 077 before invoking it so newly created output files are accessible only to their owner. Alternatively, explicitly redirect output to a securely created owner-only file or use an owner-only directory. Restrict permissions on existing output files separately, because changing the umask does not change their permissions.
Remediation
Patch, then assume compromise.
Install the applicable vendor security update. Ubuntu addresses this CVE in the rust-coreutils update associated with USN-9041-1 for Ubuntu 26.04 LTS; the exact fixed package version is not available in the supplied information. The implementation should create the default output file with explicit owner-only permissions, consistent with GNU coreutils behavior.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-35367 exploited in the wild?
- As of Nov 14, 2026, Mallory has no reports of CVE-2026-35367 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-35367?
- Yes. As of Nov 14, 2026, Mallory has reports of a public exploit for CVE-2026-35367.
- Is there a patch for CVE-2026-35367?
- Install the applicable vendor security update. Ubuntu addresses this CVE in the rust-coreutils update associated with USN-9041-1 for Ubuntu 26.04 LTS; the exact fixed package version is not available in the supplied information.
- What products are affected by CVE-2026-35367?
- Uutils Coreutils.
- How severe is CVE-2026-35367?
- CVE-2026-35367 has a CVSS v3.1 score of 3.3 (Low) and an EPSS score of 0.11% (2nd percentile) as of Nov 14, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.