🔍 Read the full analysis: OpenSSH SSHole Bug: What Happens When An SSH Password Is Too Long on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
OpenSSH fixed CVE-2026-123158, nicknamed SSHole, in version 10.6p2. The password bypass affects only a specific combination of Linux, musl, non-PAM password checking and account settings; administrators should update and restart sshd or disable password authentication while they investigate.
OpenSSH released version 10.6p2 on November 5 to fix a password-authentication bypass that can let an attacker into certain Linux accounts using an overlong password. Tracked as CVE-2026-123158 and nicknamed “SSHole,” the flaw is limited to systems running OpenSSH with the musl C library, without PAM-based password checks, and with password authentication enabled.
The issue occurs when sshd checks a password without PAM and calls the C library function crypt(). Alpine Linux’s advisory says musl returns an asterisk (*) as an error indicator when the supplied password exceeds 256 bytes. On affected systems, that can match the asterisk stored for accounts without a usable password, causing authentication to succeed. The advisory says passwords between 257 and 1,024 bytes can trigger the behavior.
The flaw requires several conditions to coincide. According to Alpine, the system must run Linux with musl, sshd must check passwords without PAM, password authentication must be enabled, and an account must have a * password field. At least one local account must also have a password hash beginning with $5$ or $6$. The Alpine advisory says one such account can make accounts with the asterisk field reachable.
OpenSSH 10.6p2 contains the fix. Alpine has published fixed packages for its branches, including older releases, and advises administrators to restart sshd after upgrading because replacing the package does not replace the running daemon. If updating is not possible immediately, the source recommends setting PasswordAuthentication no and checking authentication logs for unexpected password logins to accounts that should not accept passwords.
SSHole: When a Password Is Too Long
CVE-2026-123158 can bypass password checks on a narrow set of Linux systems. Exposure depends on the library, SSH configuration and account settings working together.
When systems may be exposed
The advisory’s conditions must coincide for the bypass to apply.
The affected SSH service uses the musl C library.
Password authentication is enabled and sshd checks passwords without PAM.
An account has a * password field, and at least one local account has a hash beginning with $5$ or $6$.
Why an overlong password matters
On affected systems, an error value can match an account field that normally prevents password login.
- An account marked with * cannot authenticate using a password.
- An invalid password check should fail.
- musl crypt() returns * for passwords longer than 256 bytes.
- The matching value can cause authentication to succeed.
Scope and reported activity
Reports show active interest, but do not mean every exposed SSH server is vulnerable.
What administrators should do
Confirm the complete configuration, then patch and check the access path.
- Install the vendor’s fixed package; OpenSSH 10.6p2 contains the upstream fix.
- Restart sshd after upgrading so the running daemon uses the fix.
- If an update is not immediately possible, disable password authentication after confirming another safe access method.
- Review SSH logs for password logins to accounts expected to have no password, and check whether those accounts can gain higher privileges.
- Ask the distribution or device vendor about package status for embedded and custom builds.
A Narrow Flaw With Real Server Risk
The conditions are specific, but the impact on a matching machine can be severe: an attacker who can reach its SSH service may bypass a password check for an affected account. SSH is commonly used to administer servers and embedded devices, so a vulnerable system exposed to a network could give an intruder a route into an environment where that account has privileges.
Alpine warns that restricting direct root login may not be enough if another account can become root—for example, through passwordless doas. The advisory identifies Alpine official tiny-cloud images from versions 3.18.11 through 3.24.3 as a case where the alpine account and passwordless doas can matter once a qualifying password hash exists. Administrators should assess the full path from SSH access to elevated privileges, not just the root-login setting.
The reported pace of activity adds urgency without changing the flaw’s scope. GreyNoise and BleepingComputer reported public exploit code about four hours after the patch; GreyNoise said its sensor recorded a successful break-in about 40 hours after release. CISA added the issue to its exploited-vulnerabilities list on November 9. Those reports point to active interest, but do not establish that every exposed system—or every Linux distribution—is vulnerable.
Products Worth Considering

Apple MacBook Neo 13-inch Laptop with A18 Pro Chip, 8GB Memory, 512GB SSD, Liquid Retina Display, and Touch ID – Blush

Brother SP-1 Dye-Sublimation Printer Starter Bundle

Brother SP1 Dye-Sublimation Printer
As an affiliate, we earn on qualifying purchases.
Why the Asterisk Can Match
On Linux, an asterisk in the password field commonly marks an account that cannot authenticate with a password. The intended result is a failed login. In the configuration described by Alpine, however, musl’s error return from crypt() can be the same character as that stored field. The problem is therefore not simply that a password is unusually long: it depends on how sshd, the C library and account configuration interact.
OpenSSH says the root cause is outside sshd, although sshd can avoid the vulnerable behavior. Musl maintainer Rich Felker disputed that the issue is a musl bug, describing it instead as erroneous use by the caller; he said musl may change the mechanism in a coming release cycle. The source also reports that Debian, Ubuntu and Red Hat say their builds are not affected. Ubuntu cites its use of glibc and PAM, while Debian’s tracker rates the issue unimportant for its packages.
The researcher who found the flaw credited “agent swarms” in the discovery process. OpenSSH said it shipped a fix within a day, citing the possibility that AI agents could rediscover bugs quickly. That is relevant to the response timeline, but the immediate security guidance remains the same: identify whether a system meets the technical conditions and apply the fixed package.
“An attacker who can reach your SSH port can log in without knowing any password.”
— Alpine Linux security advisory
Which Embedded Builds Are Affected
Not every system using musl is necessarily vulnerable: the password-checking mode, sshd settings and account database must also match the advisory’s conditions. The extent of exposure across embedded and custom Linux builds remains unclear. Medcrypt reported on the oss-security mailing list on November 9 that it independently reproduced the issue, including on a stock Yocto image; that report does not establish how broadly affected Yocto deployments are configured.
The source material does not give a complete count of vulnerable systems or confirmed victims. GreyNoise’s report concerns a successful login on one of its sensors, and CISA’s listing confirms the flaw’s inclusion on its exploited-vulnerabilities list, not the number or identity of organizations compromised. The precise responsibility between sshd and musl is also disputed by the project maintainers.
Patch, Restart and Review Logs
Administrators should first check whether their systems run OpenSSH with musl and whether password authentication is handled without PAM. If the conditions apply, install the vendor’s fixed package and restart sshd. Alpine’s instructions call for upgrading the package and restarting the daemon; the source identifies OpenSSH 10.6p2 as the upstream fix.
Where an immediate update is unavailable, disable password authentication as a temporary mitigation, provided administrators have confirmed another safe access method. Review SSH logs for password logins to accounts expected to have no password, and examine whether any affected account can obtain higher privileges. Operators of embedded or custom builds should check with their distribution or device vendor for a package status and tested remediation.
Further updates may clarify the reach of the issue in Yocto and other embedded systems, as well as any changes to musl’s error handling. Until then, vulnerability status should be judged against the full configuration, rather than the distribution name alone.
Key Questions
What is the OpenSSH SSHole vulnerability?
SSHole is the nickname for CVE-2026-123158, a password-authentication bypass affecting certain OpenSSH configurations. An overlong password can cause musl’s crypt() function to return a value that matches the stored field for an account with no password.
Are Debian, Ubuntu and Red Hat systems affected?
The source reports that Debian, Ubuntu and Red Hat say their OpenSSH builds are not affected. Ubuntu cites its use of glibc and PAM. Administrators should still follow their distribution’s security advisories for their specific packages.
What should administrators do now?
Install the fixed OpenSSH package and restart sshd. If an update cannot be applied promptly, disable password authentication where safe and check logs for unexpected password access to accounts that should not accept passwords.
Does disabling root login protect a vulnerable Alpine server?
Not necessarily. Alpine warns that a different account may be able to gain root privileges through tools such as doas. Administrators should check the privileges of every account that could be reached through the vulnerable SSH configuration.
Is every musl-based Linux system vulnerable?
No. The advisory lists multiple required conditions, including password authentication without PAM, an account with a * password field, and a local account with a $5$ or $6$ hash. The source says the extent of exposure in custom and embedded builds is still unclear.
Source: ThorstenMeyerAI.com
