Cyber Resilience

CVE-2026-35387

Openbsd Openssh ≤ 10.3

Published
02 April 2026
Modified
24 July 2026
CVSS Score v3.1 3.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 27 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-35387 is a low-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Openbsd Openssh. Its CVSS base score is 3.1 (Low).

Operationally, ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

OpenSSH before 10.3 can use unintended ECDSA algorithms. Listing of any ECDSA algorithm in PubkeyAcceptedAlgorithms or HostbasedAcceptedAlgorithms is misinterpreted to mean all ECDSA algorithms.

CWE(s)
CWE-670

Related Threats

CVEs Like This One

CVE-2026-35414Same product: Openbsd Openssh
CVE-2026-60001Same product: Openbsd Openssh
CVE-2026-59999Same product: Openbsd Openssh
CVE-2026-35385Same product: Openbsd Openssh
CVE-2026-59995Same product: Openbsd Openssh
CVE-2026-59998Same product: Openbsd Openssh
CVE-2026-59997Same product: Openbsd Openssh
CVE-2026-59996Same product: Openbsd Openssh
CVE-2026-60000Same product: Openbsd Openssh
CVE-2026-35386Same product: Openbsd Openssh

Affected Assets

openbsd
openssh
≤ 10.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V9.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation at post-design stages directly exercises control-flow paths and reveals mismatches between implemented and intended behavior.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and supporting tools reduces the chance that incorrect control-flow logic is introduced in the first place.

SI-2 Flaw Remediation partial match

Flaw identification and remediation processes can locate and correct control-flow errors once they manifest as incorrect runtime behavior.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent incorrect control-flow implementations via reviews, testing, and static analysis.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect paths that deviate from intended logic.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.

A.8.28 Secure coding partial match
prevents

Secure coding standards and reviews directly target flawed control-flow implementations.

A.8.32 Change management partial match
prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References