CVE-2026-123158
Openbsd Openssh ≤ 10.6
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-123158 is a high-severity Unexpected Status Code or Return Value (CWE-394) vulnerability in Openbsd Openssh. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 3% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
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.
OWASP Top 10 for Web (2025)
Advisories
- CISA KEV: $133 million stolen from French bank via exploited service provider (Nov 9)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-117552
Vulnerability Data
sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password authentication bypass (related to misinterpretation of whether a string is intended to be a password hash). For some configurations of…
more
accounts, any password between 256 and 1024 characters succeeds. An example of a platform using musl libc without PAM is Alpine Linux.
- CWE(s)
- KEV Date Added
- 09 November 2026
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Developer testing and evaluation at post-design stages will find missing or incorrect checks for unexpected but valid return values.
Requiring documented development standards and tools can mandate exhaustive checking of all function return values.
Engineering principles such as defensive programming and complete return-value checking stop the weakness from being introduced in code.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require proper validation of all function return values and status codes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect missing checks for unexpected but valid return values.
Training can teach developers to check return values consistently, but it is a fallible human practice against a code-level defect; the strongest effect comes from secure coding standards and security testing, leaving training with a minority share of prevented instances.
Secure coding standards directly mandate checking all legitimate return values and status codes.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces instances of unchecked return values in delivered code the way those practices do, at `partial` -- the clause's declared ceiling on this verb, because the effect depends on the supplier's fallible implementation of the contracted practices.
A.8.8's reach is disclosure-based: it finds CWE-394 instances where the unchecked-return-value defect has been published as a vendor advisory or CVE in a third-party component, and the observed examples show this class does surface as CVEs. The remainder is first-party code with unchecked return values that never receives a published advisory, which A.8.8's scanning and intake do not reach.