Skip to main content
VulnerabilityPublished Updated

CVE-2026-42189: Russh · Pre-authentication allocation from the keyboard-interactive response count

Affects russhSource GCVE Database

0
Compare
Authoritative record:CVE-2026-42189· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.60.1 soon.

Data as of 12 Nov 2026, 08:06 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.60.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade russh to 0.60.1.

Affected software

ProductAffectedFixed in
crates.iorusshpkg:cargo/russhOther threatsAffected
  • >=0.0.0-0 <0.60.1
Fixed in
  • 0.60.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied. The issue is fixed in russh version 0.60.1, which limits the allocation size based on the actual packet data length. Users should upgrade to version 0.60.1 or later to mitigate this vulnerability. Servers that keep the default behavior of rejecting keyboard-interactive authentication are not affected and require no action.

Description

CVE-2026-42189 is a high-severity vulnerability in russh versions prior to 0.60.1. It involves a pre-authentication memory allocation issue triggered by a malformed keyboard-interactive authentication response. An unauthenticated client can cause the server to allocate excessive memory, potentially leading to a denial of service due to out-of-memory conditions. The issue is fixed in russh version 0.60.1 by limiting the allocation based on actual packet data size.

References

Community reviews

Loading reviews…