SSH login bypass via repeated public key
Published Sep 30, 2026 · Updated Sep 30, 2026
Authentication bypass in Apache MINA SSHD before 2.20.0 and 3.0.0-M1 through 3.0.0-M5 lets remote attackers log in with one key. The sshd-core server authentication flow counts the same public key twice instead of enforcing distinct keys across successive public-key checks. Exploitation requires possession of one accepted key and a server configured to require two different public keys; the resulting SSH session receives only the access its account permits.
Summary
What happened
Authentication bypass in Apache MINA SSHD before 2.20.0 and 3.0.0-M1 through 3.0.0-M5 lets remote attackers log in with one key. The sshd-core server authentication flow counts the same public key twice instead of enforcing distinct keys across successive public-key checks. Exploitation requires possession of one accepted key and a server configured to require two different public keys; the resulting SSH session receives only the access its account permits.
The record
- CVE
- CVE-2026-93994
- Published
- Sep 30, 2026
- Updated
- Sep 30, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache MINA SSHD
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 30, 2026CVE publishedPublication date reported by the CVE source.
- Sep 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.20.0
- Affected versionversion=3.0.0-M1 <3.0.0-M6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started