CVE-2026-35387

CVE-2026-35387 is a low-severity vulnerability in Openbsd Openssh with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-670.

Key facts

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.

Frequently asked questions

What is CVE-2026-35387?
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.
How severe is CVE-2026-35387?
CVE-2026-35387 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-35387 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-35387?
CVE-2026-35387 affects Openbsd Openssh. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-35387?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-35387 have an EU (EUVD) identifier?
Yes. CVE-2026-35387 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-18402.
When was CVE-2026-35387 published?
CVE-2026-35387 was published on 2026-04-02 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Openbsd Openssh

All CVEs affecting Openbsd Openssh →

Other CWE-670 vulnerabilities

Browse all CWE-670 vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: