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 -Vor by inspecting package metadata withdpkg -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
- 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).
- 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.
- Enable and centralise authentication logging from OpenSSH (via syslog or
sshdaudit logs). Configure alerts on failed login attempts, particularly any that succeed after multiple failures. - 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.