{"id":4283,"date":"2026-11-14T10:56:59","date_gmt":"2026-11-14T18:56:59","guid":{"rendered":"https:\/\/cyber.mag212.com\/openssh-sshole-cve-2026-123158-alpine-musl-bypass\/"},"modified":"2026-11-14T10:56:59","modified_gmt":"2026-11-14T18:56:59","slug":"openssh-sshole-cve-2026-123158-alpine-musl-bypass","status":"publish","type":"post","link":"https:\/\/cyber.mag212.com\/fr\/openssh-sshole-cve-2026-123158-alpine-musl-bypass\/","title":{"rendered":"SSHole (CVE-2026-123158)\u00a0: La faille \u00e9troite de contournement d\u2019OpenSSH que la CISA affirme \u00eatre exploit\u00e9e"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>From the <a href=\"https:\/\/cyber.mag212.com\/the-keys-were-already-inside-mag212-cyber-weekly-november-14-2026\/\">MAG212 CYBER Weekly, 14 November 2026<\/a>. Status labels: confirmed by vendor, reported by researchers, or unverified. Every command below is copied from official documentation and was <strong>not tested by MAG212<\/strong>; run it only on systems you are authorised to administer.<\/em><\/p>\n\n\n\n<p class=\"m2-status wp-block-paragraph\"><strong>Status:<\/strong> Fix <strong>confirmed by vendor<\/strong> (portable OpenSSH 10.6p2, 5 Nov). Exploitation is indicated by the CISA KEV listing (added 9 Nov, due <strong>12 Nov<\/strong>, now passed) <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-21\">[21]<\/a><\/sup>. No public source names who exploited it. The earlier draft&#8217;s sensor and briefing sources (Previdian, Defender Daily, MyCERT) are <strong>unverified<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happened<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Portable OpenSSH 10.6p2 shipped on 5 November with &#8220;a critical security workaround that affects Linux systems that use the musl libc and PAM disabled&#8221;. The project considers the root cause &#8220;outside sshd, but it is exploitable via sshd and can be avoided there&#8221; <sup><a href=\"#src-21\">[21]<\/a><\/sup>. The CVE record describes &#8220;misinterpretation of whether a string is intended to be a password hash&#8221;, where &#8220;for some configurations of accounts, any password between 256 and 1024 characters succeeds&#8221;. It is rated CVSS 3.1 8.1, and all versions before 10.6p2 are affected <sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-24\">[24]<\/a><\/sup>. The reporter was \u00d6zg\u00fcn K\u00fcltekin of Wakefield <sup><a href=\"#src-21\">[21]<\/a><\/sup>. CISA added it to KEV on 9 November <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-25\">[25]<\/a><\/sup>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who is affected<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Alpine&#8217;s advisory says <strong>all<\/strong> of the following must be true <sup><a href=\"#src-22\">[22]<\/a><\/sup>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>The SSH server has no PAM:<\/strong> it runs <code>openssh-server<\/code> (no PAM), or <code>openssh-server-pam<\/code> with <code>UsePAM no<\/code>.<\/li>\n\n<li><strong>Password authentication is on:<\/strong> <code>PasswordAuthentication yes<\/code>, which is the default.<\/li>\n\n<li><strong>An account has <code>*<\/code> in its password field.<\/strong> Examples include root, key-only users, directory users without shadow entries, or the tiny-cloud <code>alpine<\/code> user.<\/li>\n\n<li><strong>A local account has a password hash:<\/strong> at least one has a <code>$5$<\/code> or <code>$6$<\/code> hash.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Tiny-cloud images 3.18.11\u20133.24.3 ship the <code>alpine<\/code> user with a <code>*<\/code> password <strong>and passwordless <code>doas<\/code><\/strong>, which is a direct route to root <sup><a href=\"#src-22\">[22]<\/a><\/sup>. Container images built on affected Alpine bases inherit the exposure.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Alpine branch<\/th><th>Fixed <code>openssh<\/code><\/th><\/tr><\/thead><tbody><tr><td>edge<\/td><td>10.6_p2-r0<\/td><\/tr><tr><td>3.24<\/td><td>10.3_p1-r2<\/td><\/tr><tr><td>3.23<\/td><td>10.2_p1-r1<\/td><\/tr><tr><td>3.22<\/td><td>10.0_p1-r11<\/td><\/tr><tr><td>3.21<\/td><td>9.9_p2-r1<\/td><\/tr><tr><td>3.20<\/td><td>9.7_p1-r6<\/td><\/tr><tr><td>3.19<\/td><td>9.6_p1-r3<\/td><\/tr><tr><td>3.18<\/td><td>9.3_p2-r4<\/td><\/tr><tr><td>3.17<\/td><td>9.1_p1-r7<\/td><\/tr><tr><td>3.16<\/td><td>9.0_p1-r6<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The fixed point releases are 3.21.10, 3.22.8, 3.23.8 and 3.24.4 <sup><a href=\"#src-22\">[22]<\/a><\/sup>. Because distributions backport the fix (for example, 3.24 ships 10.3_p1-r2), <strong>check the package revision, not the upstream version string<\/strong> that <code>sshd -V<\/code> prints.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why this matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SSHole needs four conditions to line up, so most servers are not exposed, but CISA has listed it as exploited and its deadline has passed. Container images and appliances built on Alpine or other musl systems are exactly where unusual sshd configurations hide, which makes inventory the first job. <em>(MAG212 analysis)<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/openssh-sshole-cve-2026-123158-alpine-musl-bypass-diagram.png\"><img decoding=\"async\" src=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/openssh-sshole-cve-2026-123158-alpine-musl-bypass-diagram.png\" alt=\"Four required conditions for the OpenSSH SSHole bypass (no PAM, password authentication on, an account with an asterisk password, a hashed account present) leading to an attacker logging in with a 256 to 1024 character password.\"\/><\/a><figcaption class=\"wp-element-caption\">Diagram: MAG212 CYBER. Solid red = observed or vendor-confirmed; dashed amber = reported or unverified; green = recommended control.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How the attack works<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The attacker reaches an exposed <code>sshd<\/code> that uses password authentication.<\/li>\n\n<li>They try an account whose password field is <code>*<\/code>, sending a password 256\u20131024 characters long.<\/li>\n\n<li><code>sshd<\/code> misreads the string as a hash and accepts it.<\/li>\n\n<li>The attacker gets a shell with that account&#8217;s rights. On tiny-cloud images, passwordless <code>doas<\/code> then gives root.<\/li>\n\n<li><em>Unknown:<\/em> who is exploiting it, and at what scale.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">What defenders should look for<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Check <code>\/var\/log\/messages<\/code> for <strong><code>Accepted password for<\/code><\/strong> by accounts that have no password (<code>alpine<\/code>, root, key-only users). Review <code>doas<\/code> use, new users, new files and changes to <code>authorized_keys<\/code>. If you cannot rule out a login, <strong>treat the host as compromised<\/strong> <sup><a href=\"#src-22\">[22]<\/a><\/sup>. <strong>False positives:<\/strong> <code>Accepted password<\/code> lines for accounts that really do have passwords are normal. Failed attempts are routine scanning.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to investigate<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Inventory SSH listeners on Alpine hosts, Alpine-based containers and appliances. Use the effective-config check (SSH-1) on each. Correlate accepted logins with your access records.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Contain and remediate (in order)<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Upgrade the package and <strong>restart <code>sshd<\/code><\/strong>. Upgrading alone does not replace the running daemon <sup><a href=\"#src-22\">[22]<\/a><\/sup>.<\/li>\n\n<li>If you cannot upgrade, disable password authentication using Alpine&#8217;s documented steps (SSH-3).<\/li>\n\n<li>Rebuild affected container images.<\/li>\n\n<li>Isolate any host with a suspicious accepted login.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Verify recovery<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Run <code>sshd -T | grep -i passwordauthentication<\/code>, which should return <code>passwordauthentication no<\/code> if you applied the mitigation. Confirm the package revision against the table above.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prevention and awareness<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Prefer key-only SSH, restrict management access to a trusted network, and send authentication logs to a central collector.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Command reference: OpenSSH \/ Alpine (sources: Alpine advisory <sup><a href=\"#src-22\">[22]<\/a><\/sup>; OpenBSD sshd(8) <sup><a href=\"#src-23\">[23]<\/a><\/sup>)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">SSH-1 &#8211; Show the effective password-authentication setting<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OS \/ shell \/ tool: Linux (Alpine), root shell, <code>sshd<\/code><\/li>\n\n<li>Privileges: root<\/li>\n\n<li>Purpose: print the running configuration&#8217;s effective <code>PasswordAuthentication<\/code> value. <code>sshd -T<\/code> is &#8220;Extended test mode \u2026 output the effective configuration to stdout and then exit&#8221; <sup><a href=\"#src-23\">[23]<\/a><\/sup>.<\/li>\n\n<li>Read-only or change: <strong>Read-only<\/strong><\/li>\n\n<li>Command:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>sshd -T | grep -i passwordauthentication<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How to interpret: <code>passwordauthentication yes<\/code> means the host meets one of the exposure conditions. <code>passwordauthentication no<\/code> means the mitigation is active <sup><a href=\"#src-22\">[22]<\/a><\/sup>.<\/li>\n\n<li>Not tested by MAG212.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">SSH-2 &#8211; Apply the fixed package and restart the daemon (Alpine)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OS \/ shell \/ tool: Alpine Linux, root shell, <code>apk<\/code>, OpenRC<\/li>\n\n<li>Privileges: root<\/li>\n\n<li>Purpose: install the fixed <code>openssh<\/code> and replace the running daemon<\/li>\n\n<li>Read-only or change: <strong>Change.<\/strong> It upgrades all packages and restarts <code>sshd<\/code>, so keep an existing session open.<\/li>\n\n<li>Commands:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>apk upgrade -U -a\nrc-service sshd restart<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How to interpret: after the restart, confirm the installed <code>openssh<\/code> revision matches the fixed version for your branch.<\/li>\n\n<li>Not tested by MAG212.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">SSH-3 &#8211; Interim mitigation: disable password authentication (Alpine)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OS \/ shell \/ tool: Alpine Linux, root shell<\/li>\n\n<li>Privileges: root<\/li>\n\n<li>Purpose: remove the vulnerable password path when you cannot upgrade<\/li>\n\n<li>Read-only or change: <strong>Change<\/strong><\/li>\n\n<li>Commands, as published by Alpine <sup><a href=\"#src-22\">[22]<\/a><\/sup>:<ul><li>Alpine&#8217;s advisory also includes a <code>sed -i.bak \u2026<\/code> edit of <code>\/etc\/ssh\/sshd_config<\/code>. <strong>Copy that line verbatim from the advisory.<\/strong> MAG212 does not reproduce it. Then validate and restart:<\/li><\/ul><\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>mkdir -p \/etc\/ssh\/sshd_config.d\necho &#x27;PasswordAuthentication no&#x27; &gt; \/etc\/ssh\/sshd_config.d\/00-no-passwords.conf<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>sshd -t &amp;&amp; rc-service sshd restart<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How to interpret: <code>sshd -t<\/code> is &#8220;Test mode. Only check the validity of the configuration file and sanity of the keys&#8221; <sup><a href=\"#src-23\">[23]<\/a><\/sup>. If it prints errors, do not restart. Confirm the result with SSH-1. Make sure key-based access works before you close your session.<\/li>\n\n<li>Not tested by MAG212.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Related on MAG212 CYBER<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/cyber.mag212.com\/the-keys-were-already-inside-mag212-cyber-weekly-november-14-2026\/\">MAG212 CYBER Weekly, 14 November 2026: The keys were already inside<\/a> (full issue and PDF)<\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/subscribe-free\/\">Subscribe free to MAG212 CYBER<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><span id=\"src-1\">[1]<\/span> CISA (GitHub mirror), &#8220;Known Exploited Vulnerabilities catalog JSON, catalogVersion 2026.11.13&#8221;, 13 Nov 2026, 20:24 UTC. <a href=\"https:\/\/raw.githubusercontent.com\/cisagov\/kev-data\/main\/known_exploited_vulnerabilities.json\" rel=\"noopener\" target=\"_blank\">link<\/a><\/li>\n\n<li><span id=\"src-2\">[2]<\/span> CVE Program, &#8220;cvelistV5 CVE JSON 5 records (CVE-2026-123039, -124194, -125350, -123158, -6460 and others)&#8221;, Various, Nov 2026. <a href=\"https:\/\/github.com\/CVEProject\/cvelistV5\" rel=\"noopener\" target=\"_blank\">link<\/a><\/li>\n\n<li><span id=\"src-21\">[21]<\/span> OpenSSH, &#8220;Release notes (OpenSSH 10.6p2)&#8221;, 5 Nov 2026. <a href=\"https:\/\/www.openssh.org\/releasenotes.html\" rel=\"noopener\" target=\"_blank\">link<\/a><\/li>\n\n<li><span id=\"src-22\">[22]<\/span> Alpine Linux, &#8220;OpenSSH password authentication bypass&#8221;, 5 Nov 2026. <a href=\"https:\/\/alpinelinux.org\/posts\/2026-11-05-openssh-password-authentication-bypass\/\" rel=\"noopener\" target=\"_blank\">link<\/a><\/li>\n\n<li><span id=\"src-23\">[23]<\/span> OpenBSD, &#8220;sshd(8) manual page&#8221;, Current. <a href=\"https:\/\/man.openbsd.org\/sshd\" rel=\"noopener\" target=\"_blank\">link<\/a><\/li>\n\n<li><span id=\"src-24\">[24]<\/span> OpenSSH portable (GitHub), &#8220;Commit 4353fdc (SSHole workaround)&#8221;, Nov 2026. <a href=\"https:\/\/github.com\/openssh\/openssh-portable\/commit\/4353fdc43ef646c43a8dda7025cc1a898caf1482\" rel=\"noopener\" target=\"_blank\">link<\/a><\/li>\n\n<li><span id=\"src-25\">[25]<\/span> eSecurityPlanet, &#8220;CISA KEV adds GPUStack, FreeSWITCH, OpenSSH, IBM flaws&#8221;, 10 Nov 2026. <a href=\"https:\/\/www.esecurityplanet.com\/vulnerabilities\/news-cisa-kev-gpustack-freeswitch-openssh-ibm-november-2026\/\" rel=\"noopener\" target=\"_blank\">link<\/a><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Written and edited by El Mostafa Ouchen for MAG212 CYBER. Facts checked against the sources above as of 14 November 2026, 10:05 AM PST. Diagrams are original MAG212 CYBER illustrations.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>SSHole n'est exploit\u00e9e que lorsque quatre conditions sont r\u00e9unies sur les syst\u00e8mes bas\u00e9s sur musl comme Alpine, mais la CISA la consid\u00e8re comme vuln\u00e9rable. Comment savoir si vous \u00eates expos\u00e9 et comment y rem\u00e9dier.<\/p>","protected":false},"author":1,"featured_media":4260,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,14],"tags":[211,217,160,210,366],"class_list":["post-4283","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-critical-cves","category-vulnerabilities","tag-alpine-linux","tag-cve-2026-123158","tag-linux","tag-openssh","tag-sshole"],"_links":{"self":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4283","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/comments?post=4283"}],"version-history":[{"count":0,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4283\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media\/4260"}],"wp:attachment":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media?parent=4283"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/categories?post=4283"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/tags?post=4283"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}