CVE-2026-35339 json
uutils coreutils chmod False Success Exit Code in Recursive Mode
published 2026-04-22 6 mo ago modified 2026-10-26 13 d ago also GHSA-4x34-chg5-mwjj , EUVD-2026-24965
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
The recursive mode (-R) of the chmod utility in uutils coreutils incorrectly handles exit codes when processing multiple files. The final return value is determined solely by the success or failure of the last file processed. This allows the command to return an exit code of 0 (success) even if errors were encountered on previous files, such as 'Operation not permitted'. Scripts relying on these exit codes may proceed under a false sense of success while sensitive files remain with restrictive or incorrect permissions.
Patch / fix
- crates.io uu_chmod 0.6.0
- Uutils coreutils 0.6.0
- rust-coreutils Debian 14 0.6.0-1
debian advisories DEBIAN-CVE-2026-35339
- github.com/uutils/coreutils@abd581f commit
- github.com/uutils/coreutils#9793 pull request
- github.com/uutils/coreutils/releases/tag/0.6.0 release
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-35339 updated cvss 5.5
rust-coreutils: chmod: false success exit code in recursive mode
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | uu_chmod | <0.6.0 |
0.6.0 |
Affected products
- Uutils coreutils
Classification
References
-
github.com
/uutils/coreutils/pull/9793
patch, issue-tracking, web
-
github.com
/uutils/coreutils/commit/abd581f62e97d0b147306ac40eac13af71c6fbba
web
-
github.com
/uutils/coreutils/releases/tag/0.6.0
vendor-advisory, web, release-notes
-
github.com
/uutils/coreutils/security/advisories/GHSA-4x34-chg5-mwjj
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-35339
advisory
-
github.com
/uutils/coreutils
package
Sources
- CVE List CVE-2026-35339
- GitHub Advisory GHSA-4x34-chg5-mwjj
- NVD CVE-2026-35339
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.