Skip to main content
Mallory
HighVulnerability

CVE-2026-35338: --preserve-root Bypass in uutils coreutils chmod

Published Apr 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.3High · v3.1
EPSS0.18%7th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Uutils
IdentifiersCVE-2026-35338CWE-22 · Improper Limitation of a Pathname…

uutils coreutils chmod contains a path validation flaw in its --preserve-root safety mechanism. The implementation checks only whether the supplied recursive target path is literally "/" and does not canonicalize or fully resolve the path before applying the safeguard. As a result, alternate path forms that resolve to the root filesystem, such as "/../", or symbolic links pointing to "/", can bypass the intended protection. When chmod is invoked recursively, this allows destructive permission changes to be applied across the entire root filesystem despite --preserve-root being specified.

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 defeats the safety control intended to prevent recursive operations on the root filesystem. An attacker, script, or accidental user can trigger recursive permission changes such as chmod -R 000 against the entire system by supplying a non-canonical path or symlink that resolves to /. This can cause widespread permission loss, denial of service, operational failure of system components, and potentially complete system breakdown requiring recovery from backup or offline repair.

Mitigation

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

Until patched, do not rely on --preserve-root when invoking recursive chmod on untrusted, user-supplied, or non-canonical paths. Canonicalize and validate target paths before execution, reject path traversal variants that resolve to /, and disallow symlink targets for recursive permission changes where possible. Operationally, restrict who can run destructive recursive chmod commands and prefer explicit path validation in automation.

Remediation

Patch, then assume compromise.

Upgrade uutils coreutils chmod to a fixed version. The provided advisory states the issue is fixed in uu_chmod 0.6.0 or later, with the fix referenced in commit 413055b3, by correcting root-path resolution handling before the preserve-root comparison. Ensure deployed packages include that fix or a later backport from the vendor.

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-35338 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-35338 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35338?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-35338.
Is there a patch for CVE-2026-35338?
Upgrade uutils coreutils chmod to a fixed version. The provided advisory states the issue is fixed in uu_chmod 0.6.0 or later, with the fix referenced in commit 413055b3, by correcting root-path resolution handling before the preserve-root comparison.
What products are affected by CVE-2026-35338?
Uutils Coreutils.
How severe is CVE-2026-35338?
CVE-2026-35338 has a CVSS v3.1 score of 7.3 (High) and an EPSS score of 0.18% (7th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

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 activity3Community discussion across Reddit, Mastodon, and other social sources.