Quick answers
- Is CVE-2026-123158 exploited in the wild?
- Yes. CVE-2026-123158 is known to be exploited in the wild, first recorded on 9 November 2026. Treat it as urgent.
- How severe is CVE-2026-123158?
- Critical severity, with a CVSS score of 8.1, published 5 November 2026.
- Which products and versions are affected?
- OpenSSH before 10.6p2 on Linux with musl libc without PAM.
- Is there a fix for CVE-2026-123158?
- Yes: fixed in 10.6p2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123158 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-123158?
- Check whether you run OpenBSD Openssh or OpenSSH at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 10.6p2
Technical details
The vulnerability is a password authentication bypass in sshd when musl libc is used without PAM, caused by misinterpretation of password hash format that permits certain long passwords to be accepted for specific account configurations. This affects OpenSSH versions before 10.6p2 on Linux; the attack requires network access to sshd with password authentication enabled and can succeed against accounts with certain configurations without user interaction. The OpenSSH project has applied a workaround in the auth-passwd.c code path to reject this bypass.
Affected products
- OpenSSH OpenSSH before 10.6p2 on Linux with musl libc without PAM
Timeline
- 2026-11-05: disclosed