The cp utility in uutils coreutils fails to properly handle setuid and setgid bits when ownership preservation fails. When copying with the -p (preserve) flag, the utility applies the source mode bits even if the chown operation is unsuccessful. This can result in a user-owned copy retaining original privileged bits, creating unexpected privileged executables that violate local security policies. This differs from GNU cp, which clears these bits when ownership cannot be preserved.
CVE-2026-35350
MEDIUMNVD 6.66.6—Elevated
EchelonGraph scoreMEDIUM confidence
Score 6.6 from GitHub Security Advisory published 2026-04-22. NVD baseline CVSS 6.6; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.6Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.6
- EG Score
- 6.6(medium)
- EPSS
- 2.6%
- KEV
- Not listed
Published
April 22, 2026
Last Modified
April 24, 2026
Advisory Details (1)
Auto-updated Jun 14, 2026No patch confirmed yet.
generic
cp -p doesn't strip setuid/setgid bits when chown fails · Issue #9750 · uutils/coreutils · GitHub
https://github.com/uutils/coreutils/issues/9750Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| rust | coreutils | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Frequently asked(5)
What is CVE-2026-35350?
CVE-2026-35350 is a medium vulnerability published on April 22, 2026. The cp utility in uutils coreutils fails to properly handle setuid and setgid bits when ownership preservation fails. When copying with the -p (preserve) flag, the utility applies the source mode bits even if the chown operation is unsuccessful. This can result in a user-owned copy retaining…
When was CVE-2026-35350 disclosed?
CVE-2026-35350 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on April 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35350 actively exploited?
CVE-2026-35350 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-35350?
CVE-2026-35350 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-35350?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35350, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-35350
Is Your Infrastructure Affected by CVE-2026-35350?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.