Advisory

GHSA-pmf6-rcx4-v53v

Also known as: CVE-2026-35341

Summary

mkfifo: permissions of an existing file are changed after FIFO creation fails

Details

When mkfifo() fails (e.g. target already exists), the code shows an error but is missing a continue;, so it falls through to fs::set_permissions and changes the permissions of the pre-existing file to the default FIFO mode (0o666 & umask -> 0644).

$ touch secret; chmod 000 secret
$ coreutils mkfifo secret fifo3 fifo4
mkfifo: cannot create fifo 'secret': File exists
$ ll secret      # uutils:
prw-r--r-- secret   # changed to 644 (GNU leaves it 000)

Impact: an attacker (or user error) can relax permissions on sensitive owner-only files such as SSH private keys, exposing them to other users. Recommendation: add continue; after the error.

Remediation: Acknowledged by Canonical; fixed in PR #10376.

---
_Reported by Zellic in the *uutils coreutils Program Security Assessment* (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.8. Credit: Zellic._

_Upstream tracking issue: https://github.com/uutils/coreutils/issues/10020 · CVE-2026-35341_

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-07-06 21:53 UTC
Modified
2026-07-06 22:11 UTC

Affected packages and fixes

uu_mkfifo

crates.io · All systems

Affected

  • introduced 0, fixed 0.6.0 (semver)

Fixed versions

0.6.0

Fix

  • Fixed version 0.6.0
    cargo update -p uu_mkfifo --precise 0.6.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences