Training and CyberInsights Today

F5 ASM

17 lessons · Beginner to advanced

Policies, staging, learning, signatures, tuning, API security, logs and recovery.

F5 ASM training →

FortiWeb

17 lessons · Beginner to advanced

Server policies, profiles, ML, signatures, APIs, troubleshooting and HA.

FortiWeb training →

How to use the WAF training hub

CyberInsights Today

Daily cybersecurity analysis and practical bulletins

Understand recent vulnerabilities, threats, their impact and mitigation. When there is no worthwhile new issue, learn a security concept or defensive practice through clear explanations, illustrations and evidence.

Read CyberInsights Today →

OpenSSH Password Bypass on Alpine Linux (CVE-2026-123158): Patch and Verify

CyberInsights Today · Vulnerability analysis · By Harpreet Singh
Disclosed November 5, 2026. Sources checked November 10, 2026.

Summary. If you run an SSH server on Alpine Linux or another Linux platform built with musl, check the server package and its effective authentication settings. CVE-2026-123158 can let an unauthenticated network user sign in as certain accounts on affected configurations. OpenSSH released 10.6p2, Alpine shipped fixed packages for its branches, and CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 9. OpenSSH release notes · Alpine advisory · Official CVE record

How a failed password check can become a login

OpenSSH’s server, sshd, accepts remote logins. musl is a C library used by Alpine and other platforms. PAM, or Pluggable Authentication Modules, is a framework that can handle sign-in checks. In the affected path, sshd checks passwords using the C library. Under specific account conditions, musl’s hashing function can return an error marker that matches the stored marker for an account without a password. The comparison can treat that match as a successful password check. Alpine’s technical explanation

Conceptual attack path. This diagram illustrates the authentication failure described by Alpine.
  1. Remote request reaches an affected sshd with password sign-in enabled.
  2. On the non-PAM musl path, a hashing error returns the same marker stored for a particular account.
  3. The comparison can accept the login. The session receives that account’s permissions.

Check exposure before applying a version rule

For Alpine, check whether the SSH server uses musl with PAM disabled, accepts passwords, and has an eligible account with the relevant password marker. Alpine also identifies a prerequisite involving another local account with a compatible password hash. Check the effective policy for the intended account and source, including any Match rules. An Alpine-based container only presents this SSH entry point if it actually runs a reachable SSH server. Alpine exposure criteria

Fixed OpenSSH builds listed by the maintainers
BranchFirst fixed package or release
Portable OpenSSH upstream10.6p2
Alpine edge10.6_p2-r0
Alpine 3.2410.3_p1-r2
Alpine 3.2310.2_p1-r1
Alpine 3.2210.0_p1-r11
Alpine 3.219.9_p2-r1

Alpine lists fixes for older branches back to 3.16 as well. Its backports can carry the fix while retaining an older upstream version number. Use the vendor’s package revision for your branch. For a device or image maintained by someone else, use that supplier’s advisory and supported update. Alpine package matrix · Upstream fixed release

What the evidence says about severity and exploitation

The published CVE score is 8.1 High under CVSS v3.1. Red Hat publishes a separate 9.8 Critical under CVSS v3.1 assessment. The two vectors differ on attack complexity. CISA records active exploitation, and SANS ISC reported exploit attempts against its sensors beginning November 5. The sensor report establishes observed attempts and cannot establish which production hosts were compromised. CVSS scores and vectors · CISA KEV entry · SANS ISC sensor report

Risk assessment. Start with internet-facing systems and management hosts that accept passwords. A successful login can expose files or services the account can access. Alpine also describes configurations where a reachable account can elevate through passwordless doas. Review privileges on the account that could be reached, including access to deployment secrets or internal systems. Alpine cloud image analysis

Contain exposure, patch, and verify the running service

  1. Limit reachability now. Move management access behind a trusted network path or restrict ingress while you check exposure. If you cannot patch immediately, Alpine advises disabling SSH password authentication. Test key-based or console access first, keep your current session open, and confirm the effective setting after the change. Network restrictions reduce reachability while the fixed package repairs the server.
  2. Install the supported fix and restart. Upgrade the server package using the correct vendor branch, then restart the SSH daemon. Alpine says its package upgrade leaves a running sshd in place until you restart it. Rebuild and redeploy affected images so replacement instances also get the fix. Alpine remediation guidance
  3. Prove what is live. Record the installed package revision, confirm the listener is served by the restarted process, and test the expected key-based access in a fresh session. Where password login should be disabled, verify the effective policy for the relevant user and source and confirm ordinary password sign-in is refused in an approved test. Check every node and standby image before closing the issue.

Investigate sessions from the exposure window

Start with successful SSH password logins for accounts intended to be key-only. Alpine points to Accepted password for entries in /var/log/messages and recommends reviewing privilege escalation, newly created accounts, files and authorized keys. Correlate session times and sources with central logs and host telemetry. If the evidence indicates unauthorized access, isolate the host, preserve records and assess credential exposure under your incident response process. A successful upgrade addresses future logins. Review existing sessions and changes separately. Alpine investigation guidance

Takeaway. Check the authentication path and package revision, restart the daemon, and verify what the listener is running. Review the pre-patch exposure window separately.

Related reading on verifying a production patch · CyberInsights Today archive

Primary references

Comments

Popular posts from this blog

PHP2Shell Explained: Impact, Patches and Mitigation for CVE-2026-109618 and CVE-2026-109619

Start Here: F5 ASM Classroom — From Beginner to Advanced

Broken Object-Level Authorization (BOLA) in APIs: How to Find and Fix IDOR