Blog

Security alert: actively exploited OpenSSH flaw (CVE-2026-123158)

A flaw in OpenSSH, tracked as CVE-2026-123158, is being actively exploited. If you run your own Linux server, VPS or dedicated host, check it today. This is not a web application bug, so a web firewall does not cover it.

What happened

On 9 November 2026, BleepingComputer reported that attackers are using the flaw to run commands on Linux systems, steal credentials and keep persistent access. The same day, CISA added it to its Known Exploited Vulnerabilities catalogue. The entry for CVE-2026-123158 describes it as an authentication bypass in OpenSSH. That means an attacker may get in without valid credentials.

OpenSSH is the service most Linux web servers use for remote administration. Being listed as exploited means this is happening in the real world, not just in a lab.

Does it affect you

It may, if any of the following apply:

  • You run a VPS or dedicated server with SSH reachable from the internet.
  • You manage servers for clients, including WordPress, PHP or Node hosting.
  • You have forgotten test or staging servers that still accept SSH connections.

If you use managed or shared hosting, the provider looks after SSH. Ask them whether they have patched, and what they have checked.

Our own figures say nothing about this flaw. Across the 16 sites DBshieldX protects, we inspected 194,679 web requests this week and logged 10,498 detections. Most were automated scanners, bad bots and probing for files and paths. That is HTTP traffic, and SSH runs separately from it. Our counts cannot tell you whether anyone has tried this flaw against your servers. Check your own SSH logs for that.

What to do now

  1. Update OpenSSH today. Install the vendor-fixed release on every server through your distribution’s normal package manager, then restart the SSH service. Confirm the new version afterwards.
  2. Limit who can reach SSH. Restrict port 22 (or whichever port you use) to trusted IP addresses or put it behind a VPN. Do this even after patching.
  3. Review recent logins. Look through your authentication logs for logins you do not recognise, especially successful ones from unfamiliar locations or at odd hours.
  4. Check for persistence. Read each authorized_keys file for keys you did not add. Also look for user accounts, scheduled tasks or services you cannot explain.
  5. Rotate credentials if anything looks wrong, or if the server was exposed and unpatched. Replace SSH keys and passwords, and any secrets stored on the server, such as database passwords and API keys in configuration files.
  6. Tell your hosting provider or clients if you find signs of compromise. Rebuilding from a known-good state is safer than trying to clean a server you cannot fully trust.

The two sources above carry the most detail on affected versions and fixes. Check them and your distribution’s security notices before you patch.

See it on your own traffic.

We'll run DBshieldX in monitor mode on one of your sites for a week, free, then walk you through what it would have blocked. Nothing is blocked until you say so.