<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[sshhole: OpenSSH musl Password Bypass on Alpine and OpenWrt]]></title><description><![CDATA[<blockquote>
<p dir="auto">OpenSSH built against musl libc and running without PAM accepts any password between 257 and 1024 characters for accounts whose password field in /etc/shadow is exactly *. The accounts affected are those intentionally locked or configured for key-only authentication, including root on many Alpine cloud images, deploy users, and certain LDAP-mapped accounts.</p>
<p dir="auto">The condition is present only on musl-based systems that do not use PAM for password verification. glibc systems, systems with UsePAM yes, Dropbear, and OpenBSD are unaffected. OpenSSH 10.6p2, released 5 November 2026, contains a workaround. Alpine has backported the fix across supported and several EOL branches.</p>
</blockquote>


<div class="row mt-3"><div class="col-12 mt-3"><div class="card col-md-9 col-lg-6 position-relative link-preview p-0">



<a href="https://threatlandscape.io/blog/openssh-musl-linux-arbitrary-long-passwords-locked-accounts" title="sshhole: OpenSSH musl Password Bypass on Alpine and OpenWrt">
<img src="https://threatlandscape.io/og_blog.png" class="card-img-top not-responsive" style="max-height:15rem" alt="Link Preview Image" />
</a>



<div class="card-body">
<h5 class="card-title">
<a class="text-decoration-none" href="https://threatlandscape.io/blog/openssh-musl-linux-arbitrary-long-passwords-locked-accounts">
sshhole: OpenSSH musl Password Bypass on Alpine and OpenWrt
</a>
</h5>
<p class="card-text line-clamp-3">Critical OpenSSH authentication bypass on musl Linux without PAM: accounts locked with * accept any password 257-1024 characters long. Fixed in 10.6p2.</p>
</div>
<a href="https://threatlandscape.io/blog/openssh-musl-linux-arbitrary-long-passwords-locked-accounts" class="card-footer text-body-secondary small d-flex gap-2 align-items-center lh-2">



<img src="https://threatlandscape.io/favicon.ico" alt="favicon" class="not-responsive overflow-hiddden" style="max-width:21px;max-height:21px" />









<p class="d-inline-block text-truncate mb-0">Threat Landscape <span class="text-secondary">(threatlandscape.io)</span></p>
</a>
</div></div></div>]]></description><link>https://citiverse.it/topic/531a475e-49f5-40b5-abfb-854251c1e57b/sshhole-openssh-musl-password-bypass-on-alpine-and-openwrt</link><generator>RSS for Node</generator><lastBuildDate>Wed, 11 Nov 2026 04:00:23 GMT</lastBuildDate><atom:link href="https://citiverse.it/topic/531a475e-49f5-40b5-abfb-854251c1e57b.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 05 Nov 2026 21:05:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to sshhole: OpenSSH musl Password Bypass on Alpine and OpenWrt on Thu, 05 Nov 2026 22:42:19 GMT]]></title><description><![CDATA[<p dir="auto">It says OpenWrt is affected but it also says Dropbear isn't affected. OpenWrt uses Dropbear by default. So stock OpenWrt is <em>not</em> affected?</p>
]]></description><link>https://citiverse.it/post/https://lemmy.ca/comment/26264032</link><guid isPermaLink="true">https://citiverse.it/post/https://lemmy.ca/comment/26264032</guid><dc:creator><![CDATA[avidamoeba@lemmy.ca]]></dc:creator><pubDate>Thu, 05 Nov 2026 22:42:19 GMT</pubDate></item></channel></rss>