CVE-2026-35387: CWE-670 Always-Incorrect Control Flow Implementation in OpenBSD OpenSSH
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.
AI Analysis
Technical Summary
CVE-2026-35387 identifies a vulnerability in OpenSSH versions before 10.3 related to the handling of ECDSA algorithms in authentication configuration. Specifically, when administrators specify any ECDSA algorithm in the PubkeyAcceptedAlgorithms or HostbasedAcceptedAlgorithms settings, the software erroneously interprets this as acceptance of all ECDSA algorithms rather than the intended subset. This behavior is due to an always-incorrect control flow implementation, classified under CWE-670, which refers to logic errors that cause unintended execution paths. The consequence is that unintended or potentially weaker ECDSA algorithms may be accepted during SSH authentication, potentially weakening the cryptographic assurance of the connection. The vulnerability does not require user interaction, but does require network access and low privileges to exploit, with a high attack complexity. The CVSS v3.1 base score is 3.1, reflecting a low severity primarily due to limited impact on confidentiality and availability, and the requirement for specific conditions to exploit. No public exploits or active exploitation have been reported. The issue is resolved in OpenSSH version 10.3, where the algorithm parsing and enforcement logic has been corrected to properly restrict accepted ECDSA algorithms as configured by administrators.
Potential Impact
The primary impact of this vulnerability is a potential weakening of authentication integrity in OpenSSH connections by allowing unintended ECDSA algorithms to be accepted. This could enable attackers to exploit weaker cryptographic algorithms if they are supported by the client or server, potentially facilitating man-in-the-middle attacks or unauthorized access under certain conditions. However, the vulnerability does not directly affect confidentiality or availability of the SSH service. The requirement for network access and low privileges, combined with high attack complexity, limits the likelihood of widespread exploitation. Organizations relying on OpenSSH for secure remote access, especially those with strict cryptographic compliance requirements, may face increased risk of authentication bypass or reduced cryptographic strength until patched. The absence of known exploits in the wild reduces immediate risk but does not eliminate the need for remediation.
Mitigation Recommendations
To mitigate CVE-2026-35387, organizations should upgrade OpenSSH installations to version 10.3 or later, where the algorithm acceptance logic has been corrected. Until upgrading is possible, administrators should avoid specifying ECDSA algorithms in PubkeyAcceptedAlgorithms or HostbasedAcceptedAlgorithms configurations to prevent unintended acceptance of all ECDSA algorithms. Additionally, auditing current SSH configurations to identify and remove any ECDSA algorithm listings can reduce exposure. Employing strict cryptographic policies that prefer stronger algorithms such as Ed25519 or RSA with adequate key sizes can further mitigate risk. Monitoring SSH authentication logs for unusual algorithm negotiation patterns may help detect attempts to exploit this vulnerability. Finally, maintaining an up-to-date inventory of OpenSSH versions deployed across infrastructure and applying security patches promptly is essential to prevent exploitation.
Affected Countries
United States, United Kingdom, Germany, France, Japan, South Korea, Australia, Canada, Netherlands, Sweden, Switzerland, India
CVE-2026-35387: CWE-670 Always-Incorrect Control Flow Implementation in OpenBSD OpenSSH
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-35387 identifies a vulnerability in OpenSSH versions before 10.3 related to the handling of ECDSA algorithms in authentication configuration. Specifically, when administrators specify any ECDSA algorithm in the PubkeyAcceptedAlgorithms or HostbasedAcceptedAlgorithms settings, the software erroneously interprets this as acceptance of all ECDSA algorithms rather than the intended subset. This behavior is due to an always-incorrect control flow implementation, classified under CWE-670, which refers to logic errors that cause unintended execution paths. The consequence is that unintended or potentially weaker ECDSA algorithms may be accepted during SSH authentication, potentially weakening the cryptographic assurance of the connection. The vulnerability does not require user interaction, but does require network access and low privileges to exploit, with a high attack complexity. The CVSS v3.1 base score is 3.1, reflecting a low severity primarily due to limited impact on confidentiality and availability, and the requirement for specific conditions to exploit. No public exploits or active exploitation have been reported. The issue is resolved in OpenSSH version 10.3, where the algorithm parsing and enforcement logic has been corrected to properly restrict accepted ECDSA algorithms as configured by administrators.
Potential Impact
The primary impact of this vulnerability is a potential weakening of authentication integrity in OpenSSH connections by allowing unintended ECDSA algorithms to be accepted. This could enable attackers to exploit weaker cryptographic algorithms if they are supported by the client or server, potentially facilitating man-in-the-middle attacks or unauthorized access under certain conditions. However, the vulnerability does not directly affect confidentiality or availability of the SSH service. The requirement for network access and low privileges, combined with high attack complexity, limits the likelihood of widespread exploitation. Organizations relying on OpenSSH for secure remote access, especially those with strict cryptographic compliance requirements, may face increased risk of authentication bypass or reduced cryptographic strength until patched. The absence of known exploits in the wild reduces immediate risk but does not eliminate the need for remediation.
Mitigation Recommendations
To mitigate CVE-2026-35387, organizations should upgrade OpenSSH installations to version 10.3 or later, where the algorithm acceptance logic has been corrected. Until upgrading is possible, administrators should avoid specifying ECDSA algorithms in PubkeyAcceptedAlgorithms or HostbasedAcceptedAlgorithms configurations to prevent unintended acceptance of all ECDSA algorithms. Additionally, auditing current SSH configurations to identify and remove any ECDSA algorithm listings can reduce exposure. Employing strict cryptographic policies that prefer stronger algorithms such as Ed25519 or RSA with adequate key sizes can further mitigate risk. Monitoring SSH authentication logs for unusual algorithm negotiation patterns may help detect attempts to exploit this vulnerability. Finally, maintaining an up-to-date inventory of OpenSSH versions deployed across infrastructure and applying security patches promptly is essential to prevent exploitation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-04-02T16:52:52.884Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69cea282e6bfc5ba1ded3a5c
Added to database: 4/2/2026, 5:08:18 PM
Last enriched: 4/2/2026, 5:24:01 PM
Last updated: 4/2/2026, 7:30:34 PM
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.