Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-35363: Current-directory deletion safeguard bypass in uutils coreutils rm

Published Apr 22, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS5.6Medium · v3.1
EPSS0.14%4th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Uutils
IdentifiersCVE-2026-35363CWE-41

A path-equivalence handling flaw in the uutils coreutils rm utility allows trailing directory separators to bypass safeguards against deleting the current directory. Although the utility rejects literal dot and dot-dot operands, it fails to recognize equivalent trailing-slash forms. A recursive, forced removal using such an operand deletes the current directory's contents before reporting a misleading invalid-input error.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The vulnerability can cause recursive deletion of all files and subdirectories within the current working directory that the invoking process has permission to remove, resulting in data loss and potentially disrupting dependent applications or services. The misleading error may delay recognition of the deletion and reduce opportunities for recovery.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid invoking vulnerable uu_rm with recursive, forced removal of trailing-slash dot-directory operands, including './' and './//'. Validate operands or deploy wrapper controls that reject trailing-slash forms of '.' and '..' before invoking the utility.

Remediation

Patch, then assume compromise.

Upgrade uu_rm to version 0.6.0 or later, which contains the fix. For distribution-managed installations, apply the applicable rust-coreutils security update; Ubuntu addresses this CVE in USN-9041-1.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
UutilsCoreutilsapplication
FAQ

Frequently asked questions

Is CVE-2026-35363 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-35363 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35363?
Yes. As of Nov 14, 2026, Mallory has reports of a public exploit for CVE-2026-35363.
Is there a patch for CVE-2026-35363?
Upgrade uu_rm to version 0.6.0 or later, which contains the fix. For distribution-managed installations, apply the applicable rust-coreutils security update; Ubuntu addresses this CVE in USN-9041-1.
What products are affected by CVE-2026-35363?
Uutils Coreutils.
How severe is CVE-2026-35363?
CVE-2026-35363 has a CVSS v3.1 score of 5.6 (Medium) and an EPSS score of 0.14% (4th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.