CVE-2026-35363 is a path-handling logic flaw in the rm utility of uutils coreutils. The implementation is intended to block deletion of the current directory and parent directory by refusing literal . and .. targets, but it fails to normalize or equivalently recognize trailing-slash variants such as ./ and .///. As a result, commands such as rm -rf ./ bypass the safeguard and proceed to recursively delete the contents of the current working directory. The issue is compounded by misleading error reporting: after the destructive operation, the command may emit cannot remove './': Invalid input, obscuring that recursive deletion has already occurred and potentially delaying response and recovery efforts.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Invalid input error after the deletion activity, operators may not immediately recognize the extent of the damage, reducing the window for incident response and data recovery.If you can’t patch tonight, do this now.
rm with trailing-slash forms of dot directories, including ./, .///, and analogous variants of ... Where feasible, use the GNU rm implementation instead of the vulnerable uutils version. Additional defensive measures include wrapper scripts, shell aliases, policy controls, or input validation that reject recursive deletion requests targeting normalized forms of . or ...Patch, then assume compromise.
uu_rm to version 0.6.0 or later. The provided advisory states the issue is fixed in commit d0e5af23. If packaging or downstream distributions ship uutils coreutils separately, ensure the installed rm implementation includes that fix rather than relying solely on package version naming.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.