CVE-2026-123158
Confirmed exploited in the wild ExploitedOpenBSD OpenSSH — OpenBSD OpenSSH Unexpected Status Code or Return Value Vulnerability
Why it matters
Exploited in the wild · public exploit available · patch/mitigation per vendor
What to do
Apply the vendor's fix or mitigation now, starting with internet-facing systems, and check logs for signs of exploitation.
Description
Published 2026-11-05sshd 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 accounts, any password between 256 and 1024 characters succeeds. An example of a platform using musl libc without PAM is Alpine Linux.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit & advisory signals
Exploited in the wildPublic exploits & proof-of-concept
Untrusted code · review only in an isolated labCVE-2026-123158 SSHole — OpenSSH authentication bypass via musl crypt() overflow on Alpine Linux (Exploit PoC)
Exploit para explotar la vulnerabilidad CVE-2026-123158 (conocida como sshole).
Audit & interim mitigation for CVE-2026-123158 (*SSHole) — OpenSSH password bypass on musl/Alpine — across Docker containers, images and host
CVE-2026-123158
Scanner CVE-2026-123158 *SSHHole
OpenSSH + musl password authentication bypass (sshole) checker: local precondition audit + remote verification; for authorized testing
Prova de conceito para exploração da vulnerabilidade CVE-2026-123158.
sshole (CVE-2026-123158): OpenSSH password bypass on alpine Linux
CVE-2026-123158 SSHole PoC
Read-only check for CVE-2026-123158: is your Alpine sshd affected by the password authentication bypass, fixed, or still running the old daemon? Tested on Alpine 3.21 to 3.24 and edge.
Vulnerability research, PoC reproduction lab, and technical analysis for Alpine Linux OpenSSH authentication bypass (CVE-2026-123158 / sshole)
OpenSSH sshole(CVE-2026-123158) 알파인 sshd 점검을 벨로키와 쉽게 보기
Patches, advisories & references
Remediation
- What to do
- Apply the vendor's fix or mitigation now. If none exists yet, restrict or disconnect the affected system until one does.
- Exploitation confirmed
- Nov 9, 2026
- Ransomware use
- Not known
Related research
reports mentioning CVE-2026-123158Intel updated 2026-11-16 16:04 UTC
Not sure whether this affects you?
Citadel's CTI team maps vulnerabilities like this one to your exposed systems and suppliers.
Talk to our CTI team