Syself security assessment
sshd in OpenSSH before 10.6p2 on Linux, when musl libc is used without PAM, lacks a workaround for a password authentication bypass (related to misinterpretation of whether a string is intended to be a password hash). For some configurations of accounts, any password between 256 and 1024 characters succeeds. An example of a platform using musl libc without PAM is Alpine Linux.
Syself Autopilot is fully managed Kubernetes on your own Hetzner servers. Every cluster runs a versioned cluster stack release, and this page tracks how CVE-2026-123158 affects the openssh component those releases ship, based on Syself's assessments. For the general description and scoring of the vulnerability, see the references.
Syself Kubernetes is not affected by CVE-2026-123158 in any of the 10 releases that ship openssh.
Reason: The vulnerable code is not included.
This flaw only affects SSH servers built against the musl C library without PAM. These nodes use the GNU C library with PAM enabled and keep SSH password login disabled, so the vulnerable code path is not present.
Syself Security| Releases | Component | Status | Reason | Fixed in | Assessment |
|---|---|---|---|---|---|
| openssh 10.4p1, 10.5p1, 10.6p1, 10.6p2 | Not affected | The vulnerable code is not included | — | Details |
Scanners such as Trivy and Grype match package versions, so they report CVE-2026-123158 whenever the vulnerable version is present, even when it cannot be exploited. Syself publishes its assessments as a VEX (Vulnerability Exploitability eXchange) document for every release. Pass it to your scanner to drop the findings Syself has assessed as not affected or fixed:
trivy image --vex hetzner-apalla-1-36-v10-advisory.openvex.json <image>
grype <image> --vex hetzner-apalla-1-36-v10-advisory.openvex.json Each assessment applies to the package version it names. A finding stays in the report when the document has no assessment for that package, or when the vulnerability is still affected or under investigation.
Download the OpenVEX document for 1.36 v10The severity shown is the upstream rating of the vulnerability itself. The status is Syself's assessment of whether it can be exploited in the components Syself ships, so a critical vulnerability can still be not affected.
Think this assessment is wrong, or found a vulnerability in Syself? Contact us.