Attackers exploit 'SSHole' authentication bypass in OpenSSH
SecurityWeek reports that exploitation attempts against an OpenSSH authentication bypass dubbed 'SSHole' have begun. The initial attempts are attributed to botnets and crypto miners, and other threat actors are expected to follow.
Written by a model from the sources below. Verify against them.
- Kind
- Vulnerability
- Vendor
- OpenSSH
- Product
- OpenSSH
- Status
- Confirmed
- First seen
- Confirmed
What to do
Update OpenSSH to a patched release as soon as one is available from your distribution or vendor
Restrict SSH access to trusted networks or VPNs until patched
Review authentication logs for unexpected successful logins
Identify OpenSSH versions in use and apply the vendor patch as soon as it is available
Rotate credentials on any host that may have been exposed
Timeline
- Made public by Mastodon1 day
- First seen by cve.now2 days
- Record last updated
- Confirmed as CVE-2026-123158
On X 10
Evidence 9
- SocialMastodon
“Within nine hours of being made public, the SSHole flaw (CVE-2026-123158) was exploited by hackers, highlighting the alarming speed at which cyber threats can spread.”
- SocialMastodon
“Patch OpenSSH immediately — there is no negotiating with CVE-2026-123158.”
- Socialoss-security
“Re: "sshole": password authentication bypass: OpenSSH + musl libc”
+1 more: oss-security - SocialMastodon
“OpenSSH vulnerability CVE-2026-123158 (SSHole) is under active exploitation within hours of disclosure.”
- SocialMastodon
“An attacker reaching SSH on certain musl-based Linux systems, including Alpine Linux, may log in to accounts that should not accept passwords.”
Show all 9 sourcesShow fewer sources
- Socialr/cybersecurity
“Under specific conditions, an attacker with network access to the SSH service can authenticate to an account that has no password configured by sending an unusually long password.”
- SocialMastodon
“The OpenSSH SSHole vulnerability is being actively exploited against Alpine Linux honeypots, prompting urgent upgrades to OpenSSH 10.6p2.”
- PressSecurityWeek
“The initial exploitation attempts are attributed to botnets and crypto miners, but other threat actors are expected to follow suit.”
- PressBleepingComputer
“Hackers are actively exploiting the "SSHole" vulnerability (CVE-2026-123158) in OpenSSH to execute commands, steal credentials, and establish persistent access.”
+1 more: BleepingComputer on Bluesky
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about SZB-44f5e7b0cb
Has OpenSSH confirmed it?
Yes. Confirmed as CVE-2026-123158.Source: Mastodon, Mastodon, oss-security, Mastodon, Mastodon, r/cybersecurity, Mastodon, SecurityWeek, BleepingComputer
What should OpenSSH users do?
Update OpenSSH to a patched release as soon as one is available from your distribution or vendor. Restrict SSH access to trusted networks or VPNs until patched. Review authentication logs for unexpected successful logins. Identify OpenSSH versions in use and apply the vendor patch as soon as it is available. Review authentication and system logs for unexpected logins or new persistence mechanisms. Rotate credentials on any host that may have been exposed.
Does it have a CVE?
Yes. It is tracked as CVE-2026-123158.Source: CVE-2026-123158