CVE-2026-93994: Red Hat Authentication bypass via duplicate public key presentation
This Red Hat advisory covers CVE-2026-93994 in Red Hat Hardened Images, OpenShift Developer Tools and Services and Red Hat build of Apache Camel 4 for Quarkus 3.
Key facts
- Vendor rating
- High, CVSS 8.1
- 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, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- 2.19.0
- Fixed in
- 2.20.0, 3.0.0, maven3-9-main-3.9.16-0.3.hum1 and 1 more below
- Source published
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
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.
When the server is configured to require multiple Secure Shell (SSH) public keys for authentication, it fails to verify that the submitted keys are distinct. A remote user can exploit this flaw by presenting the same public key twice to satisfy multi-key authentication requirements.
An attacker who possesses one valid SSH key authorized for an account can successfully authenticate by presenting the same key twice, bypassing the requirement for a second key.
Text from the source record.
How to fix CVE-2026-93994
Upgrade to a fixed release named by Red Hat:
- 2.20.0
- 3.0.0
- maven3-9-main-3.9.16-0.3.hum1
- RHSA-2026:71541
Vendor 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.
End-of-life dates for Red Hat Enterprise Linux
CVE-2026-93994 in other vendors' advisories
- Apache: CVE-2026-93994, high severity, fixed in 2.20.0, 3.0.0-M6
- Atlassian: CVE-2026-93994, high severity, fixed in Fisheye/Crucible: 4.9.15 recommended
More Red Hat Linux advisories
CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-freeCVE-2026-125350Nov 10, 2026Use after free in XMLCVE-2026-114713Nov 8, 2026Command injection via unescaped message tagCVE-2026-90436Nov 6, 2026Remote code execution via insecure deserialization of SOAP fault messagesCVE-2026-123158Nov 5, 2026Password authentication bypass via password hash misinterpretationCVE-2026-115731Nov 3, 2026authenticated remote code execution via report event deserialization
Get an email when Red Hat RHEL & SELinux publishes the next one.
See Red Hat RHEL & SELinux'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.