Skip to main content
VulnerabilityPublished

CVE-2026-35361: Uutils coreutils · Improper Preservation of Permissions

Affects Uutils coreutilsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.4 Low : upgrade to 0.6.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
3.4Low
How severe the flaw is on the 0–10 CVSS scale.
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:H/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade Uutils coreutils to 0.6.0.

Affected software

ProductAffectedFixed in
UutilscoreutilsAffected
  • <0.6.0
Fixed in
  • 0.6.0
GitHubuutils/coreutilspkg:github/uutils/coreutilsOther threatsAffected
  • =0
Fixed in–
GitHubcoreutilspkg:github/coreutilsOther threatsAffected
  • <0.6.0
Fixed in
  • 0.6.0

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 be aware of the risk of mislabeled device nodes when using the mknod utility in uutils coreutils and consider alternative methods or manual verification of device node labels after creation.

Description

CVE-2026-35361 is a vulnerability in the mknod utility of uutils coreutils where device nodes are created before their SELinux security labels are set. If the labeling fails, the cleanup attempt does not remove the improperly labeled device nodes, leaving them with default contexts that may allow unauthorized access. This issue relates to improper preservation of permissions due to non-atomic handling of security labels.

References

Community reviews

Loading reviews…