Alpine Linux

OpenSSH flaw opens Alpine Linux systems to unauthorized access

A newly disclosed vulnerability in OpenSSH lets unauthenticated attackers log into accounts with no usable password.

3 min readInfoQ
OpenSSH flaw opens Alpine Linux systems to unauthorized access

The *sshole vulnerability in OpenSSH is a reminder that the smallest assumptions about system configuration can create the largest holes in security. The flaw, tracked as CVE-2026-123158, lets an unauthenticated attacker log into accounts that have no usable password, and it is already being exploited in the wild against Alpine Linux systems. This is not an obscure edge case, it is a concrete failure mode for environments that deliberately chose a minimal, secure-by-default stack.

What makes this worth our attention is how it connects to broader conversations about trust in the software supply chain. We recently discussed how Securing the software supply chain starts with earning digital trust is not just a technical problem but a relational one. That piece, featuring OpenSSF's Christopher Robinson, emphasized that trust must be built into the process of building and distributing software, not retrofitted after an incident. The *sshole vulnerability tests that idea directly: Alpine Linux is a popular base image for containers, and its use of musl and omission of PAM were deliberate design choices for size and simplicity. Those choices opened a door that attackers are now walking through.

The practical consequence for our readers is immediate. If you run Alpine Linux systems with OpenSSH and without PAM, you are exposed right now. Attackers do not need credentials to gain access to accounts that were never intended to have them. This is not a theoretical risk. The exploitation in the wild means that patching is urgent, not optional. And this is where the story intersects with another we covered recently: How Uber's framework keeps autonomous AI agents secure and context-aware. Uber's approach to agent security acknowledges that traditional identity controls are insufficient when systems make autonomous decisions. The same principle applies here: a passwordless account is not an edge case to ignore, it is a boundary condition that must be explicitly managed. If your infrastructure relies on Alpine's minimal configuration as a security assumption, that assumption just broke.

The takeaway is straightforward: do not assume that a system designed to be minimal is automatically secure. Every configuration choice, including the absence of PAM or the use of musl, is a tradeoff that must be revisited when a vulnerability like this surfaces. The open question worth watching is whether the OpenSSH and musl maintainers will coordinate on a permanent fix that does not simply push the burden back onto users to reconfigure their systems. Until then, the only safe path is to patch, audit accounts, and treat every unauthenticated login vector as a potential breach.

From InfoQ

A recently disclosed vulnerability in OpenSSH lets an unauthenticated attacker log into accounts that should have no usable password. The issue, named *sshole and tracked as CVE-2026-123158, affects Linux systems running OpenSSH with the musl C library and which don't use PAM. Security researchers now report that attackers are exploiting it in the wild.

Read the original at InfoQ