Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-102821

russh: russh: Denial of Service via unbounded memory exhaustion during stalled key renegotiation

Overview

Published
29 Sep 2026
Modified
30 Sep 2026
Medium CVE
1 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

Russh is a Rust SSH client and server library. Prior to 0.63.2, an authenticated remote peer can send SSH_MSG_KEXINIT without the required SSH_MSG_KEX_ECDH_INIT and then flood SSH_MSG_CHANNEL_OPEN messages while SessionKexState::InProgress prevents priority_receiver in russh/src/server/session.rs from being drained. The server continues processing network input and enqueues a ChannelOpenReply for each request on an unbounded channel, allowing one connection to grow memory until the process is terminated. This issue is fixed in version 0.63.2.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Weakness: CWE-400, CWE-770

Affected packages · 1

Packages affected by CVE-2026-102821
EcosystemPackageVulnerableFixed in
Cargo (Rust) russh <0.63.2 0.63.2

Open a package to see all its vulnerabilities.

Operating systems · 3 fixes

chainguard 1 release · 1 package

fixed 1
yazi
chainguard fixes for CVE-2026-102821
ReleasePackageFixed in
yazi 26.9.1-r1

debian 1 release · 1 package

fixed 1
rust-russh
debian fixes for CVE-2026-102821
ReleasePackageFixed in
14 rust-russh 0.64.1-1

wolfi 1 release · 1 package

fixed 1
yazi
wolfi fixes for CVE-2026-102821
ReleasePackageFixed in
yazi 26.9.1-r1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.