mkfifo: permissions of an existing file are changed after FIFO creation fails

When `mkfifo()` fails (e.g. target already exists), the code shows an error but is missing a `continue;`, so it falls through to `fs::set_permissions` and changes the permissions of the pre-existing file to the default FIFO mode (`0o666` & umask -> `0644`). ``` $ touch secret; chmod 000 secret $ coreutils mkfifo secret fifo3 fifo4 mkfifo: cannot cr...

📋 Executive Summary

🧮 Severity Anatomy — CVSS 3.1 vector, decoded from the primary record

The base score summarizes severity in one number; the vector explains why. Each row below is a direct read of the official CVSS vector — verifiable against the NVD record.

⚠️ Business Impact Analysis

• ⚠️ Privilege escalation — local attacker can become SYSTEM/root

🔗 Representative Attack Path

A typical attack path for this vulnerability class, mapped to MITRE ATT&CK. This is a representative model to guide detection and defense — not a claim of observed activity against a specific target. Confirm specifics against the primary sources below.

⚠ Deep Dive Analysis

This high-severity vulnerability in rust uu_mkfifo (CVSS 7.1) represents a significant attack surface. SENTINEL APEX assesses exploitation to be technically feasible with moderate effort. Organizations running uu_mkfifo in internet-facing or privileged positions face immediate risk.

SENTINEL APEX URGENCY: ELEVATED. Score: 41/100 LOW. Patch before exploitation activity begins.

🧠 Structured Intelligence Assessment

SENTINEL APEX analytical tradecraft separates verified fact from labeled assessment and states intelligence gaps explicitly. Confidence reflects evidentiary support, not certainty.

✔ Verified Facts

• Affected CVE(s): CVE-2026-35341, CVE-2026-35341.
• Affected technology: rust uu_mkfifo.
• CVSS base score of 7.1 assigned by an authoritative source.

🧩 Analyst Assessments

• MEDIUM CONF Technical severity is assessed as high (CVSS 7.1); realized business impact depends on asset exposure and data classification.

❓ Intelligence Gaps

• No confirmed public IOCs are available at report time; detection currently relies on behavioral analytics.
• In-the-wild exploitation is unconfirmed as of this report.
• Attribution to a specific threat actor is not established by the available evidence.
• The source lacks sufficient technical detail for confident MITRE ATT&CK mapping.

🔮 Forward Outlook

• LOW CONF Exploitation activity may emerge as technical details become public; monitor vendor advisories.

🧬 Prior Intelligence Context

This report is correlated against CYBERDUDEBIVASH SENTINEL APEX's persistent analyst memory. The following entities have been tracked in prior intelligence:

• Vendor rust — previously observed once in CYBERDUDEBIVASH intelligence since 2026-07-06 (recent: cve-2026-35338-rust-uu-chmod)

🎯 MITRE ATT&CK Mapping

🔴 CVE Reference

🔍 Detection Rules — Sigma (SIEM)

Deploy to Splunk, Elastic, Microsoft Sentinel, or QRadar. SOC Pro subscribers receive pre-compiled SIEM-native query packs updated with each pipeline run.

📡 Detection Rules — YARA (Endpoint)

Deploy to endpoint detection platforms. Enterprise subscribers receive tuned, FP-validated YARA rule packs.

🎯 Multi-Audience Intelligence Products

This single analysis is packaged for every stakeholder — from the boardroom to the SOC — plus a machine-readable feed for API and MSSP integration. Enterprise & SOC Pro subscribers receive these as structured deliverables.

🏛 Executive Advisory — CISO / Security Leadership

• Affected CVE(s): CVE-2026-35341, CVE-2026-35341.
• Affected technology: rust uu_mkfifo.
• CVSS base score of 7.1 assigned by an authoritative source.

📋 Board Brief

• A high-severity cyber threat affects rust uu_mkfifo.
• Technical severity is rated 7.1/10.
• Primary exposure is operational disruption, data loss, and potential regulatory liability (e.g. GDPR, NIS2, DORA, SOC 2) where in-scope systems are affected.
• Mitigation depends on vendor guidance and compensating controls.
• Recommended posture: authorize prioritized remediation and confirm detection coverage with the security team.

🛡 SOC Bulletin

Severity HIGH · Detection coverage: 0 technique(s) across behavioral analytics · 0 network rule(s)

• P1: Sweep 14 days of telemetry for the mapped ATT&CK techniques.
• P2: Update threat-intel platform and downstream detection feeds with confirmed indicators.

🛡️ SOC Response Playbook

• 1IMMEDIATE (0-1hr): Identify all instances of uu_mkfifo in your environment via CMDB/asset inventory
• 2IMMEDIATE (0-1hr): Apply vendor patch — no maintenance window exception for LOW threats
• 3IMMEDIATE (1-2hr): If no patch available: implement WAF rules, ACLs, or network-level compensating controls
• 4SHORT-TERM (2-4hr): Deploy Sigma detection rule to SIEM — validate alert generation in test environment
• 5SHORT-TERM (4-8hr): Review logs for exploitation indicators (anomalous uu_mkfifo requests, error spikes)
• 6SHORT-TERM (8-24hr): Hunt for post-exploitation: new admin accounts, scheduled tasks, lateral movement
• 7MONITOR: Subscribe to rust security advisories for patch updates
• 8ONGOING: Track SENTINEL APEX intelligence feed for follow-on campaigns targeting uu_mkfifo

📎 Intelligence References

• github.com/advisories/GHSA-pmf6-rcx4-v53v
• github.com/uutils/coreutils/security/advisories/GHSA-pmf6-rcx4-v53v
• nvd.nist.gov/vuln/detail/CVE-2026-35341
• github.com/uutils/coreutils/issues/10020
• github.com/uutils/coreutils/pull/10376
• 📌 NVD — CVE-2026-35341