Uutils vulnerabilities
We track 6 vulnerabilities in Uutils products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on September 18, 2026.
Latest Uutils vulnerabilities
- 7.0 High severity
coreutils: Improper Preservation of Permissions
uutils coreutils versions before 0.10.0 apply setuid or setgid mode to install destinations before finalizing ownership changes, allowing privileged users to leave setuid executables owned by the privileged invoker when ownership changes fail. Attackers can ex
- 7.8 High severity
coreutils: Untrusted Search Path
A vulnerability exists in the chroot utility of uutils coreutils when using the --userspec option. The utility resolves the user specification via getpwnam() after entering the chroot but before dropping root privileges. On glibc-based systems, this can trigge
- 7.0 High severity
coreutils: Time-of-check Time-of-use (TOCTOU) Race Condition
A Time-of-Check to Time-of-Use (TOCTOU) race condition exists in the mkfifo utility of uutils coreutils. The utility creates a FIFO and then performs a path-based chmod to set permissions. A local attacker with write access to the parent directory can swap the
- 7.7 High severity
coreutils: Improper Link Resolution Before File Access
A vulnerability in the rm utility of uutils coreutils allows a bypass of the --preserve-root protection. The implementation uses a path-string check rather than comparing device and inode numbers to identify the root directory. An attacker or accidental user c
- 7.1 High severity
coreutils: Incorrect Permission Assignment for Critical Resource
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 con
- 7.3 High severity
coreutils: Improper Limitation of a Pathname to a Restricted Directory
A vulnerability in the chmod utility of uutils coreutils allows users to bypass the --preserve-root safety mechanism. The implementation only validates if the target path is literally / and does not canonicalize the path. An attacker or accidental user can use