On this page (6 sections)

Ubuntu has published USN-9041-1, a security notice for uutils coreutils, the Rust reimplementation of common Unix commands such as mkfifo, dd, tail, sort, cp and mv. The notice lists several bugs where the uutils version behaves differently from the GNU tools it replaces. For the items the research shows in full, Ubuntu describes a local attacker as the one who could abuse them.

If you run Ubuntu servers, shared hosting boxes, CI runners or containers where uutils coreutils is installed, this is worth a routine patch cycle. These are not described as remote attacks, but local flaws matter on multi-user systems and on servers where a web application compromise gives an attacker a low-privilege shell.

What the notice covers

Ubuntu's notice describes each issue in one sentence. The research excerpt of the notice is cut off in the mv item, so the mv description, the full list and the fixed package versions per Ubuntu release are not confirmed here. Read the notice itself for the exact versions.

Issues named in USN-9041-1 (Ubuntu's description)
CVEToolWhat Ubuntu says happensImpact stated by Ubuntu
CVE-2026-35341mkfifoKeeps processing when the target already exists and applies default permissions to itA local attacker could possibly obtain sensitive information or modify file permissions unexpectedly
CVE-2026-35344ddSuppresses errors during file truncationA local attacker could possibly cause silent data corruption
CVE-2026-35345tailFollows symbolic links with --follow=nameA local attacker could possibly obtain sensitive information
CVE-2026-35348sortCrashes on filenames with non-UTF-8 bytesA local attacker could possibly cause a denial of service
CVE-2026-35350cpPreserves setuid and setgid bits when ownership changes failA local attacker could possibly gain elevated privileges
Not shownmvDescription cut off in the research excerptUnconfirmed

Technical details in plain terms

These are cases where a Rust rewrite did not match the safety behavior of the GNU original. Three have full advisories in the research, so the detail below covers those three.

mkfifo changes permissions of an existing file (CVE-2026-35341)

According to the GitHub advisory, when mkfifo fails because the target already exists, the code prints an error but is missing a continue, so it still runs the permission-setting step. The existing file ends up with the default FIFO mode, which is typically 0644 after umask. The advisory's example shows a file with mode 000 becoming readable by others, where GNU leaves it untouched. The practical risk is that an owner-only file such as an SSH private key becomes readable by other users.

The CVSS 7.1 score (High) comes from the advisory's vector: local, low complexity, low privileges, high confidentiality and high integrity impact. The advisory lists affected versions of the uu_mkfifo crate as below 0.6.0, patched in 0.6.0. It says the finding was reported by Zellic in a security assessment prepared for Canonical, and that the fix is in upstream pull request #10376.

The advisory names upstream issue #10020 as its upstream tracking issue. That issue is titled as a time-of-check to time-of-use race: it describes mkfifo performing a path-based permission change after creating the FIFO, which an attacker with write access to the directory could try to redirect with a symlink swap. Its commits drop the path-based chmod, and it was closed as fixed by #10376. Note that the issue and the advisory describe the problem differently (a path-based chmod race versus a missing continue after a failed create), so check the upstream changes for the exact scope of the fix rather than assuming they are one and the same.

tail follows a symlink it should not (CVE-2026-35345)

Per the GitHub advisory, with --follow=name the uutils tail keeps watching a path after it has been replaced by a symbolic link, then prints the target's contents. If root tails a log directory that a local user can write to, that user could swap a log file for a link to a sensitive file such as /etc/shadow and read it through root's tail. The score is 5.3 (Medium), with high attack complexity. Affected versions are listed as 0.8.0 and earlier, with no patched version given in that advisory.

dd hides truncation errors (CVE-2026-35344)

The advisory says dd discards the result of truncation attempts. That mimics GNU behavior for special files like /dev/null, but also hides failures on regular files when a disk is full or a filesystem is read-only. A backup or migration script could report success while the destination holds old or garbage data. It is rated Low (3.3), but the damage is quiet, which is why it matters for backup jobs. Affected versions are 0.8.0 and earlier, with no patched version listed in the advisory.

sort, cp and mv

For the remaining items the research has only Ubuntu's one-line descriptions: sort crashing on non-UTF-8 filenames (denial of service) and cp keeping setuid and setgid bits when ownership changes fail (possible privilege escalation). The research has no CVSS scores or vectors for them, and the mv description is cut off, so treat their severity as unconfirmed until you read the notice.

Who is realistically exposed

  • Systems where uutils coreutils is installed and its commands are actually used, for example as a replacement for GNU coreutils. Systems that only use GNU coreutils do not run this uutils code.
  • Multi-user servers, shared hosting and build machines, where untrusted local users or jobs exist.
  • Servers where a web application flaw could hand an attacker a low-privilege shell. These bugs could then help with reading files or changing permissions.
  • Backup, migration and log-watching scripts that call dd, tail with name-following, or mkfifo as root.
The research does not say which Ubuntu releases ship uutils coreutils or which package names carry the fix. Check the notice for your release rather than assuming.

How to check your systems

This read-only command, run on an Ubuntu host, lists installed packages with coreutils in the name. Look for any entry that refers to uutils or a Rust coreutils build.

List installed packages that mention coreutils (Ubuntu/Debian, read-only)Shell
dpkg -l | grep -i coreutils

This shows which file the tail command resolves to and the first lines of its version output, so you can tell which implementation provides it. Compare the output with what the notice says about the affected package.

Check which implementation provides tail (read-only)Shell
readlink -f "$(command -v tail)"
tail --version | head -n 2

This lists packages with pending upgrades so you can see whether a coreutils-related fix is waiting for you.

Show pending upgrades (Ubuntu/Debian, read-only)Shell
apt list --upgradable 2>/dev/null | grep -i coreutils

What to do now

  1. Read USN-9041-1 and note the fixed package versions for your Ubuntu release.
  2. Find out whether your hosts actually use uutils coreutils, using the checks above.
  3. Install the updated packages through your normal update process, then confirm the installed version matches the notice.
  4. Check scripts run as root that use tail --follow=name, mkfifo, dd or cp on directories writable by other users, and tighten directory permissions where you can.
  5. Review permissions on sensitive files such as SSH private keys (they should be owner-only, mode 600 or stricter) in case mkfifo was ever run against them.
  6. Make backup and migration jobs verify results, for example by checking file sizes or checksums, instead of trusting dd's exit status alone.
Caution. Updating core system utilities touches commands used by many scripts. Apply the update in a maintenance window or on a staging host first, and keep a second session open while you test.

This refreshes the package index and installs all pending updates on Ubuntu or Debian. Run it as root or with sudo, then re-run the version checks above.

Apply pending package updates (Ubuntu/Debian; run as root or with sudo)Shell
sudo apt update
sudo apt upgrade

Because the dd and tail advisories list no patched upstream version, a fix may depend on the packaged version Ubuntu ships. Confirm against the notice instead of relying on the upstream version number alone.

Detection and monitoring afterwards

Local flaws leave few network traces, so focus on the host. Audit permission changes on sensitive paths such as ~/.ssh, watch for symlinks appearing in log directories that privileged tools follow, and alert on unexpected setuid or setgid files. Keep an inventory of which servers run uutils so future notices are quick to triage.

If a web-facing site shares a host with other users, the more useful long-term control is keeping an attacker from getting a local shell at all. Regular outside-in checks with Webforta Scan can help you review your public sites, and our guide to website security for small business covers the wider basics. These do not replace patching the operating system.

For other recent Ubuntu notices, see our write-ups on USN-9045-1 for the Linux kernel and USN-9037-1 for HPLIP.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-35341 - GitHub Advisory Databasegithub.com
  2. mkfifo TOCTOU race via path-based chmod · Issue #10020 · uutils/coreutilsgithub.com
  3. CVE-2026-35344 - GitHub Advisory Databasegithub.com
  4. CVE-2026-35345 - GitHub Advisory Databasegithub.com
  5. USN-9041-1: uutils coreutils vulnerabilitiesubuntu.com ·
  • Ubuntu
  • USN
  • coreutils
  • Rust
  • local privilege
  • Linux servers