Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-fw5c-8223-6h42

russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)

CVSS 4.3 MediumEPSS 0.0026 · 17th percentile

Published by the GitHub Advisory Database at 30 Oct 2026, 22:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
russhcrates.io>=0.60.0, <0.650.65
Identifiers
GHSA-fw5c-8223-6h42 · CVE-2026-116774
Weakness (CWE)
CWE-400 · CWE-835
Tags
Published
30 Oct 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

russh versions 0.60.0 up to but not including 0.65 accept a peer's channel maximum packet size of 0 without checking it. A connected peer that sends this value can make writes on that channel through the AsyncWrite path, such as Channel::data() or into_stream(), hang forever without returning an error. Upgrade to russh 0.65, the fixed version.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 17th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.