Skip to content
VulniPulse
High 3 vendors · 3 advisories

CVE-2026-93994: Apache MINA SSHD: Repeated-publickey policy bypass on server

CVE-2026-93994 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
High
CVSS base score
8.1 (Apache), 8.1 (Atlassian), 8.1 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N · base score 8.1, scored by apacheAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: none.
Weakness
  • CWE-304 Missing critical step in authentication
EPSS
0.30% chance of exploitation in the next 30 days (23rd percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
Fixed releases
  • Apache: 2.20.0, 3.0.0-M6
  • Atlassian: Fisheye/Crucible: 4.9.15 recommended
  • Red Hat: 2.20.0, 3.0.0, maven3-9-main-3.9.16-0.3.hum1, RHSA-2026:71541
Vendor advisories
3 from Apache, Atlassian, Red Hat
Assigned by
apache (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-93994; each belongs to its advisory, not to every product listed. How records are collected and checked.

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.

Text from the CVE.org record (apache).

How do I fix CVE-2026-93994?

Upgrade to a fixed release named by the vendor:

  • Apache: 2.20.0, 3.0.0-M6
  • Atlassian: Fisheye/Crucible: 4.9.15 recommended
  • Red Hat: 2.20.0, 3.0.0, maven3-9-main-3.9.16-0.3.hum1, RHSA-2026:71541
  • Users are recommended to upgrade to version 2.20.0 or 3.0.0-M6, which fix this issue. (Apache)
  • Upgrade to a fixed version listed by Atlassian: Fisheye/Crucible: 4.9.15 recommended. (Atlassian)
  • There is no mitigation available for this issue. Apply updates as they become available from Red Hat product teams. As a temporary workaround, if using Apache MINA SSHD with multi-key authentication configured, consider implementing additional authentication mechanisms (password, OTP) or restricting SSH access to trusted networks until patches are applied. (Red Hat)

Vendor advisories for CVE-2026-93994

Apache

1 advisory
  • Advisory severityHigh8.1

    High [CVE-2026-93994] Apache MINA SSHD is a Java library for client-side and server-side SSH

    CVE-2026-93994Source published Source updated

    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.

    Related products — impact not confirmed
    • Apache MINA SSHD
    Source-reported affected versions
    • 2.19.0
    Source-reported fixed versions
    • 2.20.0
    • 3.0.0-M6
    Mitigation guidance
    • Users are recommended to upgrade to version 2.20.0 or 3.0.0-M6, which fix this issue.

Atlassian

1 advisory

Red Hat

1 advisory
  • Advisory severityHigh8.1

    High [CVE-2026-93994] Authentication bypass via duplicate public key presentation

    CVE-2026-93994Source published Source updated

    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. When the…

    Affected products in this advisory
    • Red Hat Hardened Images
    • OpenShift Developer Tools and Services
    • Red Hat build of Apache Camel 4 for Quarkus 3
    • Red Hat build of Apache Camel for Spring Boot 4

    5 more entries in the full advisory.

    Source-reported affected versions
    • 2.19.0
    Source-reported fixed versions
    • 2.20.0
    • 3.0.0
    • maven3-9-main-3.9.16-0.3.hum1
    • RHSA-2026:71541
    Mitigation guidance
    • There is no mitigation available for this issue. Apply updates as they become available from Red Hat product teams. As a temporary workaround, if using Apache MINA SSHD with multi-key authentication configured, consider implementing additional authentication mechanisms (password, OTP) or restricting SSH access to trusted networks until patches are applied.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache