yamux
Affected
- introduced
0, fixed0.13.10(semver)
Fixed versions
0.13.10
Fix
- Fixed version
0.13.10cargo update -p yamux --precise 0.13.10
Advisory
Also known as: CVE-2026-32314
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
Summary
The Rust implementation of Yamux can panic when processing a crafted inbound Data frame that sets SYN and uses a body length greater than DEFAULT_CREDIT (e.g. 262145).
On the first packet of a new inbound stream, stream state is created and a receiver is queued before oversized-body validation completes. When validation fails, the temporary stream is dropped and cleanup may call remove(...).expect("stream not found"), triggering a panic in the connection state machine.
This is remotely reachable over a normal Yamux session and does not require authentication. kind of vulnerability is it? Who is
Attack Scenario
An attacker that can establish a Yamux session with a target node can crash the target by sending a single validly encoded Yamux Data|SYN frame with an oversized body:
This can trigger a panic (stream not found) and terminate the process, depending on host application panic policy.
Patches
Users should upgrade to yamux v0.13.10
This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program
High Basis: The source's own band: HIGH
0, fixed 0.13.10 (semver)0.13.10
0.13.10cargo update -p yamux --precise 0.13.10Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0