Is CVE-2026-35341 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35341 being exploited in the wild.

How severe is CVE-2026-35341?

High severity, with a CVSS score of 7.1, published 22 April 2026.

Which products and versions are affected?

uu_mkfifo (crates.io) < 0.6.0, SEMVER:introduced=0,fixed=0.6.0.

Is there a fix for CVE-2026-35341?

Yes. uu_mkfifo (crates.io): upgrade to 0.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35341 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-35341?

Check whether you run uu_mkfifo (crates.io) or Uutils Coreutils at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35341: uutils coreutils improper permission assignment in mkfifo

Q: Is there a fix for CVE-2026-35341?

Yes. uu_mkfifo (crates.io): upgrade to 0.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-35341 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-35341?

Check whether you run uu_mkfifo (crates.io) or Uutils Coreutils at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35341 · Severity: high · CVSS 7.1 · Published 2026-04-22

A vulnerability in the uutils implementation of the mkfifo command can cause existing files to have their security permissions unintentionally weakened. If a user attempts to create a new pipe (FIFO) at a location where a file already exists, the tool fails to stop and instead resets the existing file's permissions to a default public-readable state. This could allow a local attacker to gain access to sensitive private data, such as SSH keys, that were previously restricted.

Technologies: Uutils Coreutils. Vendors: crates.io, Uutils.

Quick answers

Is CVE-2026-35341 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35341 being exploited in the wild.
How severe is CVE-2026-35341?: High severity, with a CVSS score of 7.1, published 22 April 2026.
Which products and versions are affected?: uu_mkfifo (crates.io) < 0.6.0, SEMVER:introduced=0,fixed=0.6.0.
Is there a fix for CVE-2026-35341?: Yes. uu_mkfifo (crates.io): upgrade to 0.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35341 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-35341?: Check whether you run uu_mkfifo (crates.io) or Uutils Coreutils at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

uu_mkfifo (crates.io): upgrade to 0.6.0 or later
```
cargo update -p uu_mkfifo
```

Technical details

A logic error in the mkfifo implementation of uutils coreutils leads to an improper preservation of permissions (CWE-281). When mkfifo() fails because the target path already exists, the program fails to execute a 'continue' statement and instead falls through to a 'set_permissions' call. This causes the pre-existing file's permissions to be modified to the default FIFO mode (typically 0644 after umask). A local attacker can exploit this to relax permissions on sensitive files owned by other users. The issue is fixed in version 0.6.0.

Affected products

uutils coreutils (uutils) < 0.6.0

Identifiers

CVE-2026-35341
GHSA-pmf6-rcx4-v53v

Timeline

2026-01-03: disclosed: Initial issue reported on GitHub
2026-01-21: patched: Fix merged in PR #10376
2026-04-22: advisory: CVE-2026-35341 assigned and published by NVD
2026-07-06: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.