This week's thread is how little time there is between a fix and an attack. An OpenSSH bug on Alpine Linux was exploited about 40 hours after the patch came out, and a self-hosted AI model server joined the list of attacked software the same day.
Alongside that, Node.js and Go both shipped scheduled security releases, and PostgreSQL 14 gets its last update today. None of these need anything clever. They need an upgrade, a rebuild and a restart.
SSHole: any long password opens some Alpine accounts
On 5 November OpenSSH released
10.6p2 to fix a password
authentication bypass in sshd, nicknamed SSHole and tracked as
CVE-2026-123158 (CVSS 8.1). It only affects Linux systems that use the musl
C library without PAM, and the best-known example is Alpine Linux's standard
openssh-server package.
The cause is outside OpenSSH. When musl's password hashing gets a very long
password, it returns * as an error value. Accounts that have no usable
password store exactly * in /etc/shadow, so the comparison matches and the
login succeeds. On an affected account, any password of a few hundred
characters works.
A public exploit appeared within hours. GreyNoise recorded the first successful
attack on 7 November, and CISA added the bug to its
catalogue of actively exploited vulnerabilities
on 9 November. Attackers were seen reading SSH keys, querying cloud metadata
and adding their own keys to authorized_keys.
According to Alpine's advisory, a machine is exposed when all of these are true:
- it runs
openssh-server, oropenssh-server-pamwithUsePAM no; PasswordAuthenticationisyes;- some account has
*as its password field, such asrooton recent base images or a key-only user; - at least one other account has a real password hash.
Ordinary Docker containers built on Alpine are not affected unless they run
sshd inside the container.
What to do:
- Run
apk upgrade -U -a, thenrc-service sshd restart. The upgrade does not restart a daemon that is already running. Stable branches get backported fixes, sossh -Vcan still report an older version once patched; check the package revision against Alpine's table instead. - Or turn off password logins with
PasswordAuthentication no. Test key login from a second session before you restartsshd. - If a machine was exposed, look for successful password logins to accounts
whose password field is
*, and for SSH keys you did not add.
GPUStack: unauthenticated admin access to AI servers
CVE-2026-102895 (CVSS 9.8) is in
GPUStack,
an open-source cluster manager for serving AI models on your own GPUs. Before
version 2.2.0, GPUStack treated any request that appeared to come from
127.0.0.1 as the built-in administrator, and that was the default. A request
passed through a reverse proxy on the same host, or one carrying a forged
X-GPUStack-Real-IP header, looked local.
That gave an unauthenticated attacker full admin access: creating persistent API keys, reading worker and cloud-provider secrets, and running code on the host. Exploitation was observed in the wild against a 2.1.1 deployment, and CISA added it to its exploited list on 9 November.
If you run GPUStack, upgrade to 2.2.0 or later, then rotate the API keys and any cloud credentials it held. The general lesson applies to every self-hosted model server: keep the admin interface off the public internet, and never trust a client IP header your own proxy did not set.
Node.js: security releases for 22, 24 and 26
As announced in our last issue, Node.js shipped its November security release on 11 November, in 26.13.1, 24.22.3 and 22.23.5.
Seven of the fixes are rated high, and nearly all of them are in the built-in HTTP/2 and TLS servers. Several let a remote client crash a server, one can leak server memory into a request body over HTTPS, and one lets a TLS 1.2 client use renegotiation to get around client certificate authentication. If your app terminates HTTP/2 or TLS in Node itself, or relies on mTLS, this one matters. Apps behind a proxy that terminates TLS are less exposed, but should still update.
Release lines that have reached end of life, Node.js 20 and older, are affected
and get no fix. Update your Node version, rebuild and redeploy. For a container
image, rebuild on an updated base image such as node:24, and check that
node --version reports at least the fixed version.
Go: 1.27.4 and 1.26.11
The Go team released
Go 1.27.4 and 1.26.11 on
10 November with fixes for twelve CVEs in cgo, the go command, the compiler,
the linker and the net/http package.
Go compiles the standard library into your binary, so a new Go install fixes
nothing until you rebuild. Bump the toolchain or Go version in your build
image or CI, rebuild every service and redeploy. The same applies to Go tools
you ship as binaries, such as CLIs and sidecars.
PostgreSQL 14 gets its last update today
PostgreSQL 14 reaches end of life today, 12 November. The update round scheduled for today, 18.7, 17.12, 16.16, 15.20 and 14.25, is the final release for 14. After it, there are no more security or bug fixes for that version.
This round fixes over 140 bugs, and a few of them need work after updating. The release notes have the details, but in short:
- reindex GiST indexes that use
pg_trgm'sgist_trgm_ops; - reindex B-tree indexes on
bpcharcolumns declared without a length (char(n)is not affected); - reindex any GIN index you suspect is corrupted, and any table that has shown
missing chunk numbererrors; - if you use incremental backups, take a new full backup after updating.
Minor updates do not need a dump and restore. Stop the server, update the binaries and start it again.
If you are still on 14, start planning the move to a newer major version. PostgreSQL 19 is planned for 19 November, so for a production upgrade this month, 18 is the safer target.