LiveActive security incident?Get immediate response
CVE Record

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).

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A narrow but dangerous scp scenario can give downloaded files elevated execution permissions. Exposure requires an OpenSSH version before 10.3, a transfer run as root with the legacy protocol option, and omission of preserve-mode. If an affected file is later executed, the permissions could enable serious privilege and system-integrity consequences.

Executive priority

Prioritize rapid review of privileged file-transfer automation. Patch urgently where root-run legacy scp is present; otherwise handle through the normal high-severity remediation process after confirming exposure. The narrow execution conditions reduce breadth, but successful abuse could produce major privilege and system-integrity impact.

Technical view

With OpenSSH before 10.3, an scp client running as root with -O and without -p may install a received file as setuid or setgid. The supplied CVSS 3.1 score is 7.5, reflecting high complexity and required user interaction but potentially complete confidentiality, integrity, and availability impact. Distribution-specific affected package ranges are incomplete.

Likely exposure

Most exposed are systems where administrators, deployment tools, backup jobs, or scripts run legacy scp transfers as root without preserve-mode. Ordinary non-root transfers or workflows not using -O do not match the documented conditions. The supplied affected-version metadata is inconsistent, so vendor package status must be confirmed separately.

Exploitation context

The bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. Exploitation has restrictive prerequisites: a vulnerable client, root execution, legacy scp mode, omission of -p, and user participation in a download. The CVSS vector nevertheless indicates network reachability and potentially severe impact if those conditions align.

Researcher notes

The central validation target is client-side file installation behavior under the exact root, -O, and no--p combination. The supplied record's affected entry lists version "0" with default status "unaffected," which is insufficient for reliable product mapping. Consult upstream and distribution advisories for package-level determinations. No supplied source establishes public exploitation.

Mitigation direction

  • Upgrade to OpenSSH 10.3 or a vendor package explicitly documented as fixing CVE-2026-35385.
  • Until updated, prohibit root-operated scp transfers using -O without -p.
  • Remove legacy -O usage from privileged automation where compatibility testing permits.
  • For Red Hat systems, apply the relevant published erratum after confirming product and package applicability.

Validation and detection

  • Inventory OpenSSH and scp versions, identifying installations earlier than 10.3.
  • Review scripts and administrative procedures for root scp usage combining -O with omission of -p.
  • Inspect files received through matching workflows for unexpected setuid or setgid permissions.
  • Confirm distribution package remediation against applicable vendor advisories rather than upstream version numbers alone.
Prepared
Confidence
medium
Sources
7

Public sources used

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-35385 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
37Source 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9mitre
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H1.65.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-35385Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPOpenSSH: OpenSSH: Privilege escalation via scp legacy protocol when not preserving file mode
other:Red Hat severity ratingcvssV3_1
  • 2026-04-02T17:01:07.052Z: Reported to Red Hat.
  • 2026-04-02T16:30:59.615Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenBSDOpenSSH0unaffected
Weakness

CWE details

CWE-281

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-281 · source CWE mapping

Improper Preservation of Permissions

Improper Preservation of Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs