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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 15:17 UTC First seen by agentprime
- 31 Oct 2026, 15:17 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-3999-5ffv-wp2r
- OSV: GHSA-3999-5ffv-wp2r
- github.com/libp2p/rust-yamux/security/advisories/GHSA-3999-5ffv-wp2r
- nvd.nist.gov/vuln/detail/CVE-2024-32984
- github.com/libp2p/rust-yamux/commit/460baf2ccb7d5982b266cb3cb9c0bdf75b4fb779
- github.com/sigp/rust-yamux/commit/6689e227a48258a52347cd1d984adfc94afc6f7a
- github.com/libp2p/rust-yamux
- github.com/libp2p/rust-yamux/blob/yamux-v0.13.1/yamux/src/connection.rs#L289