VulnerabilityPublished 22 Apr 2026Updated 9 Nov 2026

CVE-2026-35363: Rust coreutils · A vulnerability in the rm utility of uutils coreutils allows the bypass of safeguard

Affects rust-coreutilsSource GCVE Database

Compare

Authoritative record:CVE-2026-35363· Medium 5.6

Not known to be exploited · CVSS 5.6 Medium.

Data as of 10 Nov 2026, 06:17 UTC

CVSS 3.1 base score

5.6Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSrust-coreutils`pkg:deb/ubuntu/rust-coreutils?arch=source&distro=resolute`Other threats	Affected 0.2.2-0ubuntu2 – 0.10.0-1ubuntu2~26.04.1 8 affected builds	Fixed in–
Ubuntu 25.10rust-coreutils`pkg:deb/ubuntu/rust-coreutils?arch=source&distro=questing`Other threats	Affected 0.0.30-1 – 0.2.2-0ubuntu2.1 16 affected builds	Fixed in–
Ubuntu 24.04 LTSrust-coreutils`pkg:deb/ubuntu/rust-coreutils?arch=source&distro=noble`Other threats	Affected 0.0.20-1 – 0.0.24-2 7 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should avoid using 'rm -rf' with paths that include trailing slashes equivalent to the current directory (e.g., './'). Exercise caution when running recursive delete commands and verify paths carefully.

Description

A vulnerability in the rm utility of the uutils coreutils package allows bypassing safeguards that protect the current directory from deletion. The utility correctly blocks deletion of '.' and '..' but fails to recognize equivalent paths with trailing slashes such as './' or './//'. Executing 'rm -rf ./' can silently delete all contents of the current directory while misleadingly reporting an 'Invalid input' error, potentially causing users to miss the opportunity to recover data.

Impact

The vulnerability can lead to unintended or malicious recursive deletion of all contents within the current directory. The misleading error message may delay user awareness, increasing the risk of permanent data loss. There is no indication of confidentiality or availability impact beyond data deletion. No known exploits in the wild have been reported.

Summary

The rm utility in uutils coreutils contains a flaw where it does not properly handle paths equivalent to the current directory when trailing slashes are present. Although it refuses to delete '.' or '..' directly, it fails to identify './' and similar variants as the current directory. This allows an attacker or user to run 'rm -rf ./' and recursively delete all files and subdirectories in the current directory. The command outputs a misleading error message, obscuring the actual destructive action. This vulnerability affects multiple specific versions of rust-coreutils as listed and has a CVSS 3.1 score of 5.6 (medium severity).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 06:17 UTC

Technical details

References

Community reviews

Related threats