Skip to content

← Public intelligence

crates.io package

uu_rm

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.6crates.ioPublished

    rm: 'rm -rf ./' (and ./// variants) silently deletes current directory contents, bypassing dot protection

    CVE-2026-35363 · GHSA-89p7-7cq3-hhr2

    Affected
    • crates.io uu_rm < 0.6.0
    Fixed in
    0.6.0· Vendor fix available
    Issue
    rm -rf . is correctly refused, but cleantrailingslashes normalizes ./// to ./ while pathiscurrentorparentdirectory only matches ./.. (and /.//..), not ./ or ../. So rm -rf ./ recursively deletes the directory's contents and then prints a misleading cannot remove './': Invalid input. Impact: all files/subdirectories in the current directory are silently deleted; the misleading error makes users miss the recovery window. Recommendation: handle trailing-slash variants in pathiscurrentorparentdirectory. Remediation: Acknowledged by Canonical; fixed in commit d0e5af23. --- Reported by Zellic in the uutils coreutils Program Security Assessment (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.60. Credit: Zellic. Upstream tracking issue: https://github.com/uutils/coreutils/issues/9749 · CVE-2026-35363

    Recommended action: Upgrade to 0.6.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.7crates.ioPublished

    rm: --preserve-root bypassed via a symlink to / (string check instead of dev/inode)

    CVE-2026-35349 · GHSA-7cr3-h577-g38j

    Affected
    • crates.io uu_rm < 0.7.0
    Fixed in
    0.7.0· Vendor fix available
    Issue
    The --preserve-root check uses a path-string test (path.hasroot() && path.parent().isnone()) rather than comparing device/inode. A symlink to / (e.g. /tmp/rootlink - /) has a parent component, so it passes the check. GNU caches /'s dev/inode at startup and compares every traversed directory against it. Impact: rm -rf --preserve-root on a path that resolves through a symlink to / bypasses protection and can delete system directories. Recommendation: compare each entered directory's dev/inode against cached /. Remediation: Acknowledged by Canonical; fixed in commit 5e5968cd. --- Reported by Zellic in the uutils coreutils Program Security Assessment (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.44. Credit: Zellic.

    Recommended action: Upgrade to 0.7.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →