CVE-2026-35340: Uutils coreutils · Incorrect Check of Function Return Value
Affects Uutils coreutilsSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.6.0 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:NExploitation 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 29 Oct 2026.
What to do
Upgrade Uutils coreutils to 0.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Uutilscoreutils | Affected
| Fixed in
|
GitHubuutils/coreutilspkg:github/uutils/coreutilsOther threats | Affected
| Fixed in– |
GitHubcoreutilspkg:github/coreutilsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, users should manually verify ownership changes after recursive chown or chgrp operations or use alternative tools that correctly report errors. Scripts should not rely solely on the exit code of these commands for recursive operations.
Description
A flaw in the ChownExecutor used by uutils coreutils chown and chgrp causes the utilities to return an incorrect exit code during recursive operations. The final exit code is determined only by the last file processed. If the last operation succeeds, the command returns 0 even if earlier ownership or group changes failed due to permission errors. This can lead to security misconfigurations where administrative scripts incorrectly assume that ownership has been successfully transferred across a directory tree.