CVE-2026-35385: In OpenSSH before 10.3, a file downloaded by scp may be installed setuid or setgid, an outcome contrary to...
In OpenSSH before 10.3, a file downloaded by scp may be installed setuid or setgid, an outcome contrary to some users' expectations, if the download is performed as root with -O (legacy scp protocol) and without -p (preserve mode).
Security readout for executives and security teams
Plain-English summary
This issue affects a narrow but risky OpenSSH scp workflow. If root downloads a file using legacy scp mode, the downloaded file can unexpectedly keep setuid or setgid permissions. That can turn a copied file into a privileged executable and create serious confidentiality, integrity, and availability risk.
Executive priority
Prioritize remediation on administrative hosts, build systems, backup jobs, and automation servers where root-run scp is plausible. The vulnerable condition is specific, but the impact can be high because unexpected privileged files can undermine host trust.
Technical view
CVE-2026-35385 is a CWE-281 permission-handling flaw in OpenSSH before 10.3. It applies when scp downloads are run as root with -O, using the legacy scp protocol, and without -p. Under those conditions, setuid or setgid mode may be installed unexpectedly on the downloaded file.
Likely exposure
Likely exposure is concentrated on systems where administrators or automation run scp as root with -O against OpenSSH versions before 10.3. Environments using vendor-fixed packages or avoiding legacy scp mode for privileged downloads have lower exposure.
Exploitation context
The CVSS vector indicates network reachability, high attack complexity, and required user interaction. The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat this as a serious hardening and patching issue, not a confirmed exploited-in-the-wild event.
Researcher notes
Key constraints are important: OpenSSH before 10.3, scp download, root execution, -O legacy protocol, and no -p. The provided affected metadata is limited and somewhat sparse, so product impact should be confirmed against vendor advisories before broad claims.
Mitigation direction
Upgrade OpenSSH to 10.3 or a vendor-fixed package.
Apply relevant Red Hat security advisories where applicable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-281: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
36Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.