What is CVE-2026-35361?

CVE-2026-35361 is a low-severity incorrect permission assignment for critical resource vulnerability in uu_mknod (rust), affecting versions < 0.6.0. It is fixed in 0.6.0. A file, directory, or other resource is assigned permissions that allow broader access than intended.

How severe is CVE-2026-35361?

CVE-2026-35361 has a CVSS score of 3.4 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of uu_mknod are affected by CVE-2026-35361?

uu_mknod (rust) versions < 0.6.0 is affected.

Is there a fix for CVE-2026-35361?

Yes. CVE-2026-35361 is fixed in 0.6.0. Upgrade to this version or later.

Is CVE-2026-35361 exploitable, and should I be worried?

Whether CVE-2026-35361 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-35361 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-35361 in uu_mknod

Q: How severe is CVE-2026-35361?

CVE-2026-35361 has a CVSS score of 3.4 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of uu_mknod are affected by CVE-2026-35361?

uu_mknod (rust) versions < 0.6.0 is affected.

Q: Is there a fix for CVE-2026-35361?

Yes. CVE-2026-35361 is fixed in 0.6.0. Upgrade to this version or later.

Q: Is CVE-2026-35361 exploitable, and should I be worried?

Whether CVE-2026-35361 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-35361 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-35361?

Upgrade uu_mknod to 0.6.0 or later.

Summary

mknod: Device nodes created mislabeled on SELinux, with broken cleanup (remove_dir on a node)

uutils calls mknod before setting the SELinux context (GNU uses setfscreatecon first, labeling atomically). If set_selinux_security_context fails, cleanup uses std::fs::remove_dir, which cannot remove device nodes or FIFOs, leaving the mislabeled node behind.

Impact: on SELinux-enforcing systems the node is created with the wrong context; the command reports failure but leaves a mislabeled device node that may bypass mandatory access control, and orphaned nodes can persist across reboots. Recommendation: use setfscreatecon before mknod, abort on failure, and use remove_file for cleanup.

Remediation: Acknowledged by Canonical.

Reported by Zellic in the uutils coreutils Program Security Assessment (prepared for Canonical, Jan 20 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242. Finding 3.58. Credit: Zellic.

Impact

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

CVE-2026-35361 has a CVSS score of 3.4 (Low). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.6.0); upgrading removes the vulnerable code path.

Affected versions

uu_mknod (< 0.6.0)

Security releases

uu_mknod → 0.6.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade uu_mknod to 0.6.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-35361? CVE-2026-35361 is a low-severity incorrect permission assignment for critical resource vulnerability in uu_mknod (rust), affecting versions < 0.6.0. It is fixed in 0.6.0. A file, directory, or other resource is assigned permissions that allow broader access than intended.
How severe is CVE-2026-35361? CVE-2026-35361 has a CVSS score of 3.4 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of uu_mknod are affected by CVE-2026-35361? uu_mknod (rust) versions < 0.6.0 is affected.
Is there a fix for CVE-2026-35361? Yes. CVE-2026-35361 is fixed in 0.6.0. Upgrade to this version or later.
Is CVE-2026-35361 exploitable, and should I be worried? Whether CVE-2026-35361 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-35361 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-35361? Upgrade uu_mknod to 0.6.0 or later.