Uutils coreutils up to 0.5.x Mknod Utility std::fs permissions
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Uutils coreutils up to 0.5.x. The affected element is the function std::fs of the component Mknod Utility. Performing a manipulation results in permissions.
This vulnerability was named CVE-2026-35361. The attack needs to be approached locally. There is no available exploit.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Uutils coreutils up to 0.5.x. This affects the function std::fs of the component Mknod Utility. The manipulation with an unknown input leads to a permissions vulnerability. CWE is classifying the issue as CWE-281. The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was presented by Zellic. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-35361 since 04/02/2026. The exploitability is told to be easy. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1222 for this issue.
Upgrading to version 0.6.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25004). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
Website
- Product: https://github.com/uutils/coreutils/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.7
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.4
CNA Vector (canonical): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: PermissionsCWE: CWE-281 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: coreutils 0.6.0
Timeline
04/02/2026 CVE reserved04/22/2026 Advisory disclosed
04/22/2026 VulDB entry created
07/07/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Researcher: Zellic
Status: Confirmed
CVE: CVE-2026-35361 (🔒)
GCVE (CVE): GCVE-0-2026-35361
GCVE (VulDB): GCVE-100-359013
EUVD: 🔒
Entry
Created: 04/22/2026 18:53Updated: 07/07/2026 02:07
Changes: 04/22/2026 18:53 (66), 07/07/2026 02:07 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.