CVE-2026-35361 json
uutils coreutils mknod Security Label Inconsistency and Broken Cleanup on SELinux Systems
published 2026-04-22 6 mo ago modified 2026-10-26 13 d ago also GHSA-r9hw-mj3w-phcq , EUVD-2026-25004
- cvss
- 3.4
- 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 mknod utility in uutils coreutils fails to handle security labels atomically by creating device nodes before setting the SELinux context. If labeling fails, the utility attempts cleanup using std::fs::remove_dir, which cannot remove device nodes or FIFOs. This leaves mislabeled nodes behind with incorrect default contexts, potentially allowing unauthorized access to device nodes that should have been restricted by mandatory access controls.
Patch / fix
- crates.io uu_mknod 0.6.0
- Uutils coreutils 0.6.0
- rust-coreutils Debian 14 0.6.0-1
debian advisories DEBIAN-CVE-2026-35361
- github.com/uutils/coreutils@42b2ad8 commit
- github.com/uutils/coreutils#10582 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-35361 updated cvss 4.4
rust-coreutils: mknod: security label inconsistency and broken cleanup on SELinux systems
-
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).
Exploits and checks
- github.com https://github.com/uutils/coreutils/pull/10582 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 3.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | uu_mknod | <0.6.0 |
0.6.0 |
Affected products
- Uutils coreutils
Classification
References
-
github.com
/uutils/coreutils/pull/10582
issue-tracking, patch, exploit, web
-
github.com
/uutils/coreutils/commit/42b2ad83cdcf6e959ecb378c5040c60d9c64becf
web
-
github.com
/uutils/coreutils/releases/tag/0.6.0
vendor-advisory, web, release-notes
-
github.com
/uutils/coreutils/security/advisories/GHSA-r9hw-mj3w-phcq
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-35361
advisory
-
github.com
/uutils/coreutils
package
Sources
- CVE List CVE-2026-35361
- GitHub Advisory GHSA-r9hw-mj3w-phcq
- NVD CVE-2026-35361
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.