Local permission modification after failed FIFO creation
Published Apr 22, 2026 · Updated Apr 22, 2026
Incorrect permission assignment in uutils coreutils before 0.6.0 allows local users to relax existing file permissions via mkfifo. After FIFO creation fails for an existing path, mkfifo omits a terminating continue and still passes that path to fs::set_permissions with the requested or default FIFO mode. The attacker needs local access and a target path processed by a more privileged invocation; relaxed modes expose sensitive files to other local users.
Summary
What happened
Incorrect permission assignment in uutils coreutils before 0.6.0 allows local users to relax existing file permissions via mkfifo. After FIFO creation fails for an existing path, mkfifo omits a terminating continue and still passes that path to fs::set_permissions with the requested or default FIFO mode. The attacker needs local access and a target path processed by a more privileged invocation; relaxed modes expose sensitive files to other local users.
The record
- CVE
- CVE-2026-35341
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- uutils
- Product
- coreutils
- Classifications
- CWE-732, T1222.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-pmf6-rcx4-v53v local reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo