DeFi Intel

OpenSSH Ships Urgent Workaround for Alpine Password Bypass

Key-only accounts can be exposed if SSH password authentication remains enabled. Alpine urges operators to update and restart the server process.

TL;DR

OpenSSH issued version 10.6p2 on 5 November 2026 to fix a critical authentication bypass (CVE‑2026‑123158) that let attackers log in to password‑less Alpine Linux accounts with an overlong password. The fix and Alpine patches close the flaw, but administrators must update and possibly disable password authentication to stay secure.

Key facts

  • OpenSSH released version 10.6p2 on 5 November 2026 as a critical security workaround.
  • The flaw, nicknamed “sshole,” is tracked as CVE‑2026‑123158 with a CVSS 3.1 score of 8.1 (High).
  • It affects Alpine Linux servers that run OpenSSH with musl libc and PAM disabled.
  • Exploitation requires a password between 257 and 1,024 bytes and an account whose password field is a single asterisk (*).
  • Alpine published patched OpenSSH packages for every release back to 3.16 on the same day.

OpenSSH released version 10.6p2 on 5 November 2026, delivering an emergency patch that blocks a critical authentication bypass affecting Alpine Linux servers that use the musl C library without PAM. The flaw, dubbed “sshole” and tracked as CVE‑2026‑123158, lets an unauthenticated attacker log in with a password between 257 and 1,024 bytes to any account that has no password set. The vulnerability was reported by researcher Özgün Kültekin of Wakefield and scored 8.1 (High) by the NVD.

Background

The vulnerability stems from the way OpenSSH’s sshd validates passwords when PAM is disabled. Alpine Linux’s default openssh‑server package is built without PAM, causing sshd to hash passwords directly with the system’s crypt() function. When an account’s password field contains only an asterisk (*)—the marker for a password‑less account—sshd borrows a salt from another local account that has a real SHA‑256 ($5$) or SHA‑512 ($6$) hash. Musl’s crypt() rejects passwords longer than 256 bytes for those hash types and returns an asterisk to signal the error. Because sshd then compares the returned asterisk with the stored asterisk, the overlong password is mistakenly accepted. The bug traces back to an OpenSSH change in July 2016 that introduced salt borrowing to mitigate a timing attack (CVE‑2016‑6210) and to musl changes in 2012 that altered crypt() error handling. The combination of these legacy design decisions creates a deterministic bypass that works on any server meeting four conditions: Alpine’s openssh‑server without PAM (or openssh‑server‑pam with UsePAM=no), PasswordAuthentication enabled, at least one *‑only account, and at least one other account with a $5$ or $6$ hash. The issue is confined to musl‑based Linux distributions; glibc‑based systems, non‑Linux platforms, and any configuration that routes authentication through PAM are unaffected. OpenSSH rates the fix as a critical security workaround, while Alpine has back‑ported patches to every supported release from 3.16 onward. No in‑the‑wild exploitation has been reported, and CISA does not list the flaw in its Known Exploited Vulnerabilities catalog.

What happened

On 5 November 2026 OpenSSH announced the release of Portable OpenSSH 10.6p2, describing it as a critical security workaround for Linux systems that use musl libc with PAM disabled (Source 1). The release patches the authentication bypass by refusing a match when the stored password field is shorter than four characters, effectively blocking the overlong‑password trick (Source 1). Alpine Linux published a security advisory the same day, confirming that its standard openssh‑server package is affected and that fixed packages are available for every release back to 3.16 (Source 1, Source 2). The advisory explains that an attacker needs only network reach, the name of a password‑less account, and a single SSH connection; the attack succeeds on every attempt if four conditions hold (Source 1, Source 2, Source 3). The flaw was originally reported by Özgün Kültekin of Wakefield, who named it “sshole” in his technical write‑up (Source 1, Source 3). OpenSSH developer Damien Miller urged operators to set PasswordAuthentication=no or disable SSH immediately (Source 1, Source 2, Source 3). The CVE identifier CVE‑2026‑123158 was assigned by MITRE on the day of release, receiving a CVSS 3.1 score of 8.1 (High) from the NVD (Source 1, Source 2, Source 3, Source 4). CISA’s SSVC assessment classifies exploitation as proof‑of‑concept rather than active, and the vulnerability does not appear in CISA’s Known Exploited Vulnerabilities catalog (Source 1, Source 2). No public reports of exploitation have surfaced, and the bug’s root cause is considered to lie outside sshd, in the interaction between OpenSSH’s salt‑borrowing logic and musl’s crypt() implementation (Source 1, Source 3).

Market impact

The announcement triggered immediate updates across Alpine Linux repositories, with fixed OpenSSH packages released for every branch from 3.16 to edge (Source 1, Source 2). While the sources do not provide price data, the critical rating and CVSS 8.1 score suggest heightened demand for patch management services and vulnerability scanning tools targeting musl‑based environments. Security vendors such as SOC Prime highlighted the need for detection content, potentially driving sales of their AI‑native detection platforms (Source 4). The lack of reported exploitation means that immediate financial losses for affected organizations are not documented, but the advisory’s urgency likely accelerated upgrade cycles and may have increased traffic to Alpine’s package mirrors. The NVD’s secondary CVSS score of 8.1 (High) could influence risk‑based budgeting decisions for enterprises that rely on Alpine in cloud images, edge devices, and embedded systems.

Why it matters

The bypass allows unauthenticated remote access to accounts that administrators assume are inaccessible because they have no password, undermining the security model of key‑only SSH logins. If an attacker gains a foothold on a password‑less account that can use doas or other privilege escalation mechanisms, they can potentially obtain root privileges, especially on cloud images where the alpine user is present (Source 1). The flaw’s reliance on a simple overlong password makes it trivial to weaponize, requiring only network reach and knowledge of a password‑less username. Because many Alpine deployments serve as base images for containers, appliances, and IoT devices, the vulnerability has a broad attack surface beyond traditional servers. The fact that the root cause lies in musl’s crypt() behavior means that any musl‑based distribution that disables PAM could be vulnerable, expanding the risk to OpenWrt, Buildroot, and Yocto builds that embed OpenSSH (Source 3, Source 4). The emergency nature of the patch and the advisory’s call to disable password authentication immediately underscore the potential for rapid compromise if left unaddressed.

DeFi Intel’s take

Editorial analysis, not a statement of fact.

DeFi Intel's take: the OpenSSH emergency patch highlights how legacy code interactions can create high‑impact vulnerabilities in widely used infrastructure components. We read this as a reminder that even well‑maintained projects like OpenSSH can inherit risky behavior from older libraries such as musl, especially when default configurations disable PAM. The swift coordinated response from OpenSSH and Alpine suggests that the open‑source community can move quickly when a flaw is exposed, but the reliance on manual configuration changes (disabling PasswordAuthentication) indicates a gap in default hardening. For DeFi operators that run Alpine‑based nodes or use containerised services built on musl, the advisory signals an urgent need to audit SSH settings, apply the 10.6p2 update, and verify that no password‑less accounts remain exposed. The broader lesson is that supply‑chain components—libraries, libc implementations, and authentication stacks—must be regularly reviewed to prevent similar bypasses from emerging in critical blockchain infrastructure.

Sources used for this analysis

DeFi Intel wrote this analysis from the reporting above. Any figure or quotation can be checked against those pages.

Frequently asked questions

What is the sshole vulnerability?

The sshole vulnerability (CVE‑2026‑123158) is an authentication bypass in OpenSSH that lets an attacker log in to password‑less accounts by sending an overlong password (257‑1,024 bytes) on systems using musl libc without PAM. The bug exploits how sshd borrows a salt and how musl’s crypt() returns an asterisk for long inputs, causing a false match.

Which systems are affected by CVE‑2026‑123158?

The flaw affects Linux systems that run OpenSSH on the musl C library with PAM disabled. Alpine Linux’s default openssh‑server package is the most common example, and the issue also applies to any musl‑based builds such as OpenWrt, Buildroot, or Yocto that ship OpenSSH without PAM.

What steps should administrators take to mitigate the risk?

Administrators should upgrade to OpenSSH 10.6p2 or later, apply Alpine’s patched packages for all supported releases, and consider disabling password authentication (PasswordAuthentication=no) or disabling SSH entirely on exposed systems. Verifying that no accounts have a lone asterisk in /etc/shadow and restarting the sshd service after the update are also recommended.

Direct answers

Short answers, written to be quoted.

What caused the OpenSSH authentication bypass on Alpine Linux?
The bypass was caused by OpenSSH’s salt‑borrowing logic combined with musl libc’s crypt() returning an asterisk for passwords longer than 256 bytes, which matched the stored asterisk for password‑less accounts.
How can I protect my Alpine servers from the sshole bug?
Upgrade OpenSSH to version 10.6p2 or later, apply Alpine’s patched packages for your release, and consider disabling PasswordAuthentication or SSH entirely on exposed systems.
Read full article on The Defiant →

DeFi Intel is an entity-graph aggregator: we curate, tag and link crypto news to a typed knowledge graph of protocols, tokens, people and incidents. We do not republish the full article body. Use the link above to read the original report at The Defiant.

Discussion

Comments are reviewed before publication.

No comments yet.

Want the full article?

Continue reading on The Defiant →

Stay current on entity-tagged crypto news

Get the weekly DeFi Intel brief — entity-graph intelligence covering protocols, tokens and incidents, free to your inbox.