Skip to main content
Akamai Cloud (Linode)

Customer Security Advisory: OpenSSH Password Authentication Bypass Vulnerability [CVE-2026-123158]

Degraded Lasted 0m · started · Akamai Cloud (Linode)'s page

Level
confirmed
Worst impact
Degraded
Components
Linode.com
Down Index
17of 100

What to do

  • Check whether you use Akamai Cloud (Linode) Linode.com. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-11-05 17:40 UTC and 2026-11-05 17:40 UTC may need a replay.
  • Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai Cloud (Linode) 1

  1. resolved

    Akamai is aware of the password authentication bypass vulnerability affecting certain Linux systems using musl libc that was recently mitigated by an urgent OpenSSH update . Since Alpine Linux is specifically called out as being affected, we wanted to assure customers that Linode’s Alpine images are not affected by this vulnerability. Linodes using password-less provisioning do not have password authentication enabled by default unless customers change this configuration option in sshd_config after launch, while linodes launched using a password do not have any unlocked user accounts with a password hash set to ‘*’. However, we would like to use this opportunity as a reminder for customers to consider disabling password authentication permanently in favor of more secure mechanisms such as SSH keys or SSH CA certificates.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-dd3637a877

Is Akamai Cloud (Linode) still down?

No, this incident was resolved 2026-11-05 17:40 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.

How long did it last?

0m, from 2026-11-05 17:40 UTC to 2026-11-05 17:40 UTC, by the times Akamai Cloud (Linode) posted.

What was affected?

Akamai Cloud (Linode) named Linode.com.

What caused it?

Akamai Cloud (Linode) hasn't published a root cause. If it does, it shows here.

Where does this come from?

Akamai Cloud (Linode)'s official status page, https://status.linode.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.