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

> Attackers can expose sensitive files like SSH keys by triggering permission changes on existing files when mkfifo fails to create a new FIFO.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-35341, GHSA-pmf6-rcx4-v53v, UBUNTU-CVE-2026-35341

## What is CVE-2026-35341?

CVE-2026-35341 is a high-severity missing authorization vulnerability in Uutils coreutils, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-35341?

2 open source packages ship an affected version, including uu_mkfifo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `uu_mkfifo` | crates.io | All versions | 0.6.0 |
| `uu_mkfifo` | crates.io | All versions | 0.6.0 |

Products: Uutils Coreutils.

## How do I fix CVE-2026-35341?

Upgrade uu_mkfifo to 0.6.0 or later.

## Is CVE-2026-35341 being exploited?

There is no known exploitation of CVE-2026-35341 in the wild and no public exploit code.

## Other vulnerabilities in Uutils coreutils

- [CVE-2026-35338](https://insights.sbomify.com/CVE-2026-35338/): uutils coreutils chmod Path Traversal Bypass of --preserve-root (high 7.3)
- [CVE-2026-35368](https://insights.sbomify.com/CVE-2026-35368/): uutils coreutils chroot Local Privilege Escalation and chroot Escape in via Name Service Switch (NSS) Injection (high 7.2)
- [CVE-2026-35352](https://insights.sbomify.com/CVE-2026-35352/): uutils coreutils mkfifo Privilege Escalation via TOCTOU Race Condition (high 7.0)
- [CVE-2026-35349](https://insights.sbomify.com/CVE-2026-35349/): uutils coreutils Path-Based Safety Bypass with --preserve-root (medium 6.7)
- [CVE-2026-35350](https://insights.sbomify.com/CVE-2026-35350/): uutils coreutils cp Unexpected Privileged Executable Creation with -p (medium 6.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35341 and fix it if it is affected.

What it is: CVE-2026-35341 is a high-severity missing authorization vulnerability in Uutils coreutils, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35341 in the wild and no public exploit code.

Affected packages and fixed versions:
- uu_mkfifo (crates.io): affected all versions; fixed in 0.6.0
- uu_mkfifo (crates.io): affected all versions; fixed in 0.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35341/ (Markdown: https://insights.sbomify.com/CVE-2026-35341/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35341
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35341
- OSV: https://osv.dev/vulnerability/CVE-2026-35341

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35341/
Summaries are generated and may contain mistakes; the official description above is the record.