Advisory record · GHSA-3999-5ffv-wp2r

Yamux Memory Exhaustion Vulnerability via Active::pending_frames property

CVSS 7.5 HighEPSS 0.0076 · 55th percentile

Published by the GitHub Advisory Database at 1 May 2024, 16:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
yamuxcrates.io>=0.13.0, <0.13.20.13.2
Identifiers
GHSA-3999-5ffv-wp2r · CVE-2024-32984
Weakness (CWE)
CWE-400
Published
1 May 2024
Updated
10 Sept 2026

Machine-written summary

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

The yamux crate for Rust, versions 0.13.0 up to but not including 0.13.2, does not bound its queue of pending frames, so it can grow without limit. A remote attacker can trigger frames to be queued, such as by opening a stream or sending a Ping, and then stop reading from the TCP connection so the queue is never drained. This can exhaust the node's memory until the process is terminated. Upgrade to yamux 0.13.2 or later.

Written 8 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
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0076, the 55th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:17 UTC First seen by agentprime
  2. 31 Oct 2026, 15:17 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.