CVE-2026-35349

uutils coreutils Path-Based Safety Bypass with --preserve-root

Published Apr 22, 2026 CVSS 3.1 · 6.7 Medium EPSS < 1% KEV · Not listed
Description
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 can bypass this safeguard by using a symbolic link that resolves to the root directory (e.g., /tmp/rootlink -> /), potentially leading to the unintended recursive deletion of the entire root filesystem.

Analysis

AI-generated

Technical impact

The flaw exists in the rm command of uutils coreutils. The program verifies the presence of / when the user supplies the --preserve-root flag by inspecting the path string instead of checking the underlying device and inode numbers. If a symbolic link that points to / is supplied, the check passes and the command proceeds to remove files normally. An attacker or accidental user can trigger the dangerous behavior by providing such a link, causing rm to delete the entire root filesystem recursively.

Affected Systems

The vulnerability affects the uutils coreutils package, specifically the rm utility in releases prior to v0.7.0. Any systems that rely on the uutils coreutils binary and have not applied the patch in the 0.7.0 release are potentially vulnerable.

Risk and Exploitability

The CVSS score of 6.7 indicates a moderate severity and the attack likely requires local execution with elevated privileges, as removing the root filesystem requires root or similar rights. The EPSS score of < 1% indicates a very low but non‑zero probability of exploitation, and the vulnerability is not listed in CISA's KEV catalogue, but its impact remains substantial because a single mistaken invocation can cause catastrophic data loss. Updating to a patched version negates the problem and removes the risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update uutils coreutils to version 0.7.0 or newer where the root safety check compares device and inode numbers.
  • Limit the use of rm with --preserve-root to privileged users only; enforce this through file permissions or sudoers restrictions.
  • Audit scripts and automation tools that might invoke rm and replace any hazardous uses of symbolic links pointing to root with safer alternatives or remove the links entirely.

Generated by OpenCVE AI on April 28, 2026 at 15:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-v762-x3cf-5mfg uutils coreutils has a Link Following Issue Via rm Utility
Github GHSA Github GHSA GHSA-7cr3-h577-g38j rm: --preserve-root bypassed via a symlink to / (string check instead of dev/inode)
History
Type Values Removed Values Added
First Time appeared Uutils
Uutils coreutils
CPEs cpe:2.3:a:uutils:coreutils:*:*:*:*:*:rust:*:*
Vendors & Products Uutils
Uutils coreutils
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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 can bypass this safeguard by using a symbolic link that resolves to the root directory (e.g., /tmp/rootlink -> /), potentially leading to the unintended recursive deletion of the entire root filesystem.
Title uutils coreutils Path-Based Safety Bypass with --preserve-root
Weaknesses CWE-59
References
Metrics cvssV3_1

{'score': 6.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H'}

Weaknesses
  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')

Sources

Status
PUBLISHED
Assigner
canonical
Published
Updated
Apr 22, 2026, 6:05 PM
Reserved
Apr 2, 2026, 12:58 PM
Status
Analyzed
Published
Apr 22, 2026, 5:16 PM
Modified
Oct 26, 2026, 9:10 PM