ZeroDayAlert

CVE-2026-123158: OpenBSD OpenSSH Unexpected Status Code or Return Value Vulnerability

OpenBSD OpenSSH on Linux contains an unexpected status code or return value vulnerability that could allow for authentication bypass.

OpenBSD OpenSSH Added to KEV 2026-11-09 Federal due 2026-11-12 Known ransomware use

Required action — quoted from CISA

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Where this comes from. The identifier, product, dates and required action above are copied verbatim from the CISA Known Exploited Vulnerabilities catalog. The action plan below is written by an AI agent from that record and published automatically. AssurePort has not independently tested this vulnerability and makes no claim about whether any specific system is affected.

Who is affected

OpenSSH running on Linux systems is affected by an authentication bypass vulnerability. The issue is specific to the OpenBSD implementation of OpenSSH on Linux platforms; the record does not specify which versions of OpenSSH or Linux distributions are in scope. If you run OpenSSH for remote access—whether on servers, embedded systems, or bastion hosts—you should treat this as potentially affecting your infrastructure.

How to check whether this touches you

  • Inventory all systems where OpenSSH is installed and enabled. Check your configuration management database, cloud instance metadata, and container image registries for OpenSSH presence.
  • Determine whether each OpenSSH instance is reachable from untrusted networks: check firewall rules, security groups, and network segmentation to establish whether port 22 or a forwarded alternative is exposed to the internet or to lateral-movement paths.
  • Fingerprint the running OpenSSH version on each system using ssh -V or by inspecting package metadata with dpkg -l openssh-server (Debian/Ubuntu) or equivalent. Note that some distributions backport security fixes without bumping the advertised version number, so version alone is not definitive.

What to do

  1. Obtain the vendor's patch or mitigation guidance from OpenBSD's security advisories and apply it according to CISA BOD 26-04 timelines (federal systems have a deadline of 2026-11-12; others should follow the BOD's risk-based framework).
  2. If you cannot patch immediately, restrict network access to OpenSSH: disable port forwarding, tighten firewall rules to allow SSH only from known administrative networks, and disable password authentication in favour of key-based methods if not already in use.
  3. Enable and centralise authentication logging from OpenSSH (via syslog or sshd audit logs). Configure alerts on failed login attempts, particularly any that succeed after multiple failures.
  4. If your infrastructure is cloud-hosted or uses managed services, verify with your provider that their instances are patched, or discontinue use of the affected product if mitigations are not available.

If you find you were exposed

Exploitation of authentication bypass vulnerabilities typically occurs before public disclosure, so you should search your SSH and system authentication logs backwards from the announcement date for anomalous login activity: successful logins from unexpected source addresses, logins to disabled accounts, or privilege escalation attempts. Confirm the scope of any access by checking command histories, file modification times, and lateral movement indicators. Log retention is often the limiting factor; act promptly if you have fewer than 90 days of history.

Get these the morning they land.

One email, only when a vulnerability is newly confirmed as exploited — the CISA record plus our action plan. No more than one a day, and nothing on quiet days.

Knowing it exists is not the same as knowing you are exposed.

This page can tell you that CVE-2026-123158 is being exploited. It cannot tell you whether OpenSSH is running somewhere of yours that is reachable. That question is what a scan answers.

Check your own surface →