← Back
CVE-2026-35361
Vulnerability in uu_mknod (CVE-2026-35361)
Summary
vulnerability in uu_mknod (CVE-2026-35361). Risk of unauthorized operations or information disclosure. Exploitable via ``mknod``. Mitigation: upgrade to `0.6.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-35361** has been found in uu_mknod.
Attackers can target a specific entry point like ``mknod`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade uu_mknod to **0.6.0** or later.
If unsure, ask your IT team or search "uu_mknod CVE-2026-35361" on the vendor's site.
CVE-2026-35361 (uu_mknod) — CWE-281 /
Attack surface: `mknod` / `setfscreatecon` / `set_selinux_security_context` / `remove_file`
Patched: `0.6.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-281) exists in uu_mknod. Attackers reach the vulnerable code path via ``mknod`` without authentication.
📍 Affected scope
uu_mknod — . Attack surface: `mknod` / `setfscreatecon` / `set_selinux_security_context` / `remove_file`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.6.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'uu_mknod' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'uu_mknod' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `uu_mknod` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade uu_mknod to 0.6.0ステージング環境で 0.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
uu_mknod
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.6.0"}]}]
References
- web https://github.com/uutils/coreutils/security/advisories/GHSA-r9hw-mj3w-phcq
- web https://nvd.nist.gov/vuln/detail/CVE-2026-35361
- web https://github.com/uutils/coreutils/pull/10582
- web https://github.com/uutils/coreutils/commit/42b2ad83cdcf6e959ecb378c5040c60d9c64becf
- web https://github.com/uutils/coreutils/releases/tag/0.6.0
- web https://github.com/advisories/GHSA-r9hw-mj3w-phcq