Notes · Christian Espiritu Kjeldsen
If your VPS runs Alpine Linux: update OpenSSH today.
Alpine published a password-authentication bypass on November 5, 2026. If you run sshd on Alpine and still allow password logins, an attacker who can reach port 22 can log in without knowing any password. Most WordPress hosts and Docker boxes that don't run sshd are outside this. Tiny-cloud / Alpine VPS images are the ones to check.
Checked November 6, 2026
What happened
openssh-server is built without PAM. When PasswordAuthentication is yes, and the machine has at least one account with a $5$ or $6$ password hash, an attacker can send a 257–1024 byte password to any account whose password field is * (no password set — normal for key-only users) and get in. One connection. No retries.* account + at least one local $-style hash. Official tiny-cloud images ship an alpine user with * and passwordless doas — safe on first boot, exploitable once any password hash exists.! in shadow).apk upgrade, then restart sshd. Upgrading the package alone does not replace the running daemon. If you can't update yet: set PasswordAuthentication no and restart.Which of these is your server?
Do all four boxes below today.
Keep one SSH session open. Run apk upgrade -U -a, confirm the fixed openssh package for your branch, then rc-service sshd restart. Test a new login before you close the old session. If you can't upgrade yet, disable password authentication first.
Check the OS in one command.
SSH in and run cat /etc/os-release. If you see ID=alpine, treat it as Alpine and do the four boxes. If it says Ubuntu/Debian/etc., this specific advisory doesn't apply — still worth confirming PasswordAuthentication is off unless you need passwords.
You're outside this advisory if the container doesn't run sshd.
Alpine's advisory says Docker and other container users that do not run sshd in the container are not affected. If you do expose sshd inside a container, treat it like an Alpine VPS and upgrade.
This Alpine advisory does not apply.
Still good hygiene: prefer key-only SSH, keep OpenSSH updated, and set PasswordAuthentication no unless you have a real reason for passwords. Shared WordPress hosts usually don't give you sshd config — ask the host if you're unsure.
The 4-box checklist
Tick what's true today. It builds a short to-do list you can copy. Nothing you tick leaves this page.
Commands that match Alpine's advisory
apk upgrade -U -a rc-service sshd restart # if you cannot upgrade yet: mkdir -p /etc/ssh/sshd_config.d echo 'PasswordAuthentication no' > /etc/ssh/sshd_config.d/00-no-passwords.conf sshd -t && rc-service sshd restart sshd -T | grep -i passwordauthentication
Those lines come from Alpine's own advisory. Keep an open session until a new login works. On tiny-cloud, update every running instance built before the fixed point releases.
What I'd do this week
- Find every Alpine box that answers on port 22. Side projects and staging VPS count.
- Upgrade, then restart sshd. Confirm
sshd -Tshows what you expect. - Skim the logs once. Unexpected password accepts on key-only accounts → treat as compromised, rotate keys, rebuild if you can't be sure.
What I can't tell you
I can't see your VPS from here. I don't know whether your host's image already ships PasswordAuthentication no, or whether anyone has tried the long-password login against your box. No public CVE ID was listed on Alpine's page when they published. I'm not paid by Alpine or the OpenSSH project.
Sources
Facts checked against the sources above on November 6, 2026. Not a penetration test and not legal advice. If the box holds customer data or payments, have someone who manages that host walk the audit with you.
Want a second pair of eyes on a VPS or WordPress host?
Book a free 30-minute call. We'll say plainly whether this advisory applies and what to do next.
Book a free intro call