Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-35364: Symlink race in uutils coreutils mv cross-device moves

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
CVSS6.3Medium · v3.1
EPSS0.09%0th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Uutils
IdentifiersCVE-2026-35364CWE-367 · Time-of-check Time-of-use (TOCTOU)…

CVE-2026-35364 is a time-of-check to time-of-use race condition in the uutils coreutils mv utility during cross-device moves. The utility removes the destination path before recreating it through a copy operation. A local attacker with write access to the destination directory can create a symbolic link at that path during the intervening window. The subsequent copy follows the link, allowing a privileged move to overwrite an attacker-selected target file with the source file's contents.

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.

Successful exploitation compromises file integrity by redirecting a privileged cross-device move to an unintended target. Overwriting security-sensitive files can potentially enable privilege escalation, while overwriting application or system files can cause data corruption or service disruption. The consequences depend on the moving process's privileges, the selected target, and the source file's contents.

Mitigation

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

Use GNU mv instead of the affected uutils implementation for privileged cross-device moves. Avoid privileged moves into directories writable by untrusted users, or restrict destination-directory permissions so an attacker cannot replace the destination during the copy operation. Ubuntu 26.04 retained GNU mv because of TOCTOU concerns.

Remediation

Patch, then assume compromise.

Install the applicable vendor security update for uutils coreutils. Ubuntu addresses this CVE in the rust-coreutils update associated with USN-9041-1 for Ubuntu 26.04 LTS. Exact fixed package and upstream versions are not available in the supplied information.

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-35364 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-35364 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35364?
Yes. As of Nov 14, 2026, Mallory has reports of a public exploit for CVE-2026-35364.
Is there a patch for CVE-2026-35364?
Install the applicable vendor security update for uutils coreutils. Ubuntu addresses this CVE in the rust-coreutils update associated with USN-9041-1 for Ubuntu 26.04 LTS.
What products are affected by CVE-2026-35364?
Uutils Coreutils.
How severe is CVE-2026-35364?
CVE-2026-35364 has a CVSS v3.1 score of 6.3 (Medium) and an EPSS score of 0.09% (0th 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.