VulnerabilityPublished 11 Jun 2026Updated 12 Nov 2026

CVE-2026-48110: Russh · SSH message fields allocated before their size is checked

Affects russhSource GCVE Database

Compare

Authoritative record:CVE-2026-48110· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.61.0 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.61.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade russh to 0.61.0.

Affected software

Product	Affected	Fixed in
crates.iorussh`pkg:cargo/russh`Other threats	Affected >=0.34.0 <0.61.0	Fixed in 0.61.0

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

AI-suggested

Upgrade russh to version 0.61.0 or later, where the vulnerability is fixed by rejecting oversized name-lists before allocation. Since a patch is available and fixed versions are known, applying this official fix is the recommended mitigation.

Description

The russh SSH library versions from 0.34.0 up to but not including 0.61.0 contain a vulnerability where SSH message fields are allocated before their size is checked. This allows a peer to send oversized or highly fragmented algorithm name-lists during the SSH key exchange, causing excessive memory allocation. The issue is fixed in version 0.61.0 by rejecting name-lists longer than 16 KiB or containing more than 1,024 entries before processing.

Impact

An unauthenticated remote attacker can exploit this vulnerability by sending crafted SSH messages with oversized algorithm name-lists during the initial key exchange. This can cause the russh server process to allocate excessive memory, potentially leading to denial of service through memory exhaustion. There is no impact on confidentiality or integrity reported.

Summary

In russh versions >=0.34.0 and <0.61.0, client and server message handlers decode length-prefixed strings and name-lists into owned memory structures before validating their size and content. Specifically, during the SSH_MSG_KEXINIT message in the key exchange, a malicious peer can send extremely large or fragmented algorithm name-lists, leading russh to allocate significantly more memory than the actual packet size. This can cause memory exhaustion on the server when handling many concurrent connections. The vulnerability is addressed in russh 0.61.0 by enforcing limits on name-list length (16 KiB) and entry count (1,024) before splitting and decoding.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 08:06 UTC

Technical details

References

Community reviews

Related threats