CVE-2026-93994

Apache MINA SSHD: Repeated-publickey policy bypass on server

Published Sep 30, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
Apache MINA SSHD is a Java library for client-side and server-side SSH. SSH servers can be configured to require multi-authentication schemes, for instance two different public keys, not just one. In OpenSSH, this would be done by setting in sshd_config AuthenticationMethods "publickey,publickey". Apache MINA SSHD provides an equivalent configuration mechanism.




In Apache MINA SSHD versions up to 2.19.0 and 3.0.0-M1 to 3.0.0-M5 the server code in component sshd-core does not enforce that the two public keys presented are different. A user can thus successfully authenticate with only one of the two key pairs required by presenting this single key twice. This is a partial authentication bypass.






Users are recommended to upgrade to version 2.20.0 or 3.0.0-M6, which fix this issue.

Analysis

AI-generated

Technical impact

The vulnerability in Apache MINA SSHD allows an attacker to authenticate by presenting the same public key twice when the server is configured to require two distinct keys. Because the server does not enforce key uniqueness, the attacker bypasses the intended multi‑authentication requirement, gaining unauthorized access to the SSH account. This flaw falls under CWE‑303 and CWE‑304, weaknesses that permit authentication bypass.

Affected Systems

Apache MINA SSHD, versions up to and including 2.19.0 and 3.0.0‑M1 through 3.0.0‑M5, are affected. Users should verify the specific build installed and consider it vulnerable if it falls within these ranges.

Risk and Exploitability

The CVSS score of 8.1 indicates high severity. Although the EPSS score is below 1%, indicating a low but non-zero exploitation probability, the absence of a KEV listing does not diminish the risk; the flaw is exploitable over the network via standard SSH authentication attempts. An attacker with network access can attempt to authenticate by replaying a single key, thus bypassing the multi-authentication policy. The vulnerability is readily exploitable with no special privileges required beyond the ability to initiate SSH login attempts.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache MINA SSHD to version 2.20.0 or 3.0.0‑M6, which implements proper key‑uniqueness checks.
  • If upgrading is not immediately possible, replace the vulnerable library with a trusted, non‑vulnerable version or remove the SSH component that relies on it.
  • Configure and monitor SSH authentication logs for repeated key usage and apply additional access controls or firewall restrictions to limit repeated authentication attempts.

Generated by OpenCVE AI on October 1, 2026 at 03:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Apache
Apache mina Sshd
Vendors & Products Apache
Apache mina Sshd
Type Values Removed Values Added
Description Apache MINA SSHD is a Java library for client-side and server-side SSH. SSH servers can be configured to require multi-authentication schemes, for instance two different public keys, not just one. In OpenSSH, this would be done by setting in sshd_config AuthenticationMethods "publickey,publickey". Apache MINA SSHD provides an equivalent configuration mechanism. In Apache MINA SSHD versions up to 2.19.0 and 3.0.0-M1 to 3.0.0-M5 the server code in component sshd-core does not enforce that the two public keys presented are different. A user can thus successfully authenticate with only one of the two key pairs required by presenting this single key twice. This is a partial authentication bypass. Users are recommended to upgrade to version 2.20.0 or 3.0.0-M6, which fix this issue.
Title Apache MINA SSHD: Repeated-publickey policy bypass on server
Weaknesses CWE-304
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-303

    Incorrect Implementation of Authentication Algorithm

  • CWE-304

    Missing Critical Step in Authentication

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 30, 2026, 2:29 PM
Reserved
Sep 19, 2026, 12:21 PM
Status
Awaiting Analysis
Published
Sep 30, 2026, 10:17 AM
Modified
Sep 30, 2026, 4:13 PM
Severity
Important
Public date
Sep 30, 2026, 9:45 AM