yamux
Activity
- Latest release
- 2mo ago
- Total releases
- 50
- Cadence
- ~24 days
- Last 12 months
- 5
Details
- License
- Apache-2.0 OR MIT
- First release
- Nov 09, 2018
| Version | Released | |
|---|---|---|
0.14.0
unknown
|
0.14.0
unknown
Dependencies (9)
+ 1 more |
|
0.13.10
unknown
|
0.13.10
unknown
Dependencies (9)
+ 1 more |
|
0.13.9
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.13.9
unknown
Dependencies (9)
+ 1 more |
|
0.13.8
unknown
2 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev |
0.13.8
unknown
Dependencies (9)
+ 1 more |
|
0.13.7
unknown
2 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev |
0.13.7
unknown
Dependencies (9)
+ 1 more |
|
0.13.6
unknown
2 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev |
0.13.6
unknown
Dependencies (9)
+ 1 more |
|
0.13.5
unknown
2 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev |
0.13.5
unknown
Dependencies (9)
+ 1 more |
|
0.13.4
unknown
2 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev |
0.13.4
unknown
Dependencies (9)
+ 1 more |
|
0.13.3
unknown
2 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev |
0.13.3
unknown
Dependencies (9)
+ 1 more |
|
0.13.2
unknown
2 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev |
0.13.2
unknown
Dependencies (9)
+ 1 more |
|
0.13.1
unknown
3 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev
CVE-2024-32984
GHSA-3999-5ffv-wp2r
May 01, 2024
Yamux Memory Exhaustion Vulnerability via Active::pending_frames property
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryAttack scenario The Rust implementation of the Yamux stream multiplexer uses a vector for pending frames. This vector is not bounded in length. Every time the Yamux protocol requires sending of a new frame, this frame gets appended to this vector. This can be remotely triggered in a number of ways, for example by:
Under normal circumstances, this queue of pending frames would be drained once they’re sent out over the network. However, the attacker can use TCP’s receive window mechanism to prevent the victim from sending out any data: By not reading from the TCP connection, the receive window will never be increased, and the victim won’t be able to send out any new data (this is how TCP implements backpressure). Once this happens, Yamux’s queue of pending frames will start growing indefinitely. The queue will only be drained once the underlying TCP connection is closed. Components https://github.com/libp2p/rust-yamux/blob/yamux-v0.13.1/yamux/src/connection.rs#L289 DetailsThis attack is inspired by the HTTP/2 Rapid Reset Attack (CVE 2023-44487), HTTP/2 Ping Flood (CVE-2019-9512), and the QUIC Path Validation attack (see my blog post: https://seemann.io/posts/2023-12-18-exploiting-quics-path-validation/). ImpactAn attacker can cause a remote node to run out of memory, which will result in the corresponding process getting terminated by the operating system. Depending on the application protocols running on top of rust-libp2p, higher amplification factors are possible. For example, image a protocol that sends out 10 MB of data as a result of an incoming request. By issuing that request and sending a Yamux stream window update (together ~100-200 bytes), the victim would now enqueue the entire 10 MB into its frame buffer. Any block transfer / sync protocols might be good candidates. In addition to consuming huge amounts of memory, this attack also drives up the victim's CPU load, such that the allocation of memory at some point becomes CPU-limited. This was originally submitted by @marteen-seemann to the Ethereum Foundation bug bounty program. Fixed in
0.13.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.13.1
unknown
Dependencies (9)
+ 1 more |
|
0.13.0
unknown
3 CVEs
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev
CVE-2026-31814
GHSA-4w32-2493-32g7
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed WindowUpdate credit
High
Network
Low
None
None
SumaryThe Rust implementation of Yamux accepts Attack ScenarioAn attacker that can establish a Yamux session with a target node can crash the target by sending two validly encoded Yamux frames:
ImpactRemote unauthenticated denial of service. PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.9
References
Updated Mar 16, 2026 · Source: OSV.dev
CVE-2024-32984
GHSA-3999-5ffv-wp2r
May 01, 2024
Yamux Memory Exhaustion Vulnerability via Active::pending_frames property
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
SummaryAttack scenario The Rust implementation of the Yamux stream multiplexer uses a vector for pending frames. This vector is not bounded in length. Every time the Yamux protocol requires sending of a new frame, this frame gets appended to this vector. This can be remotely triggered in a number of ways, for example by:
Under normal circumstances, this queue of pending frames would be drained once they’re sent out over the network. However, the attacker can use TCP’s receive window mechanism to prevent the victim from sending out any data: By not reading from the TCP connection, the receive window will never be increased, and the victim won’t be able to send out any new data (this is how TCP implements backpressure). Once this happens, Yamux’s queue of pending frames will start growing indefinitely. The queue will only be drained once the underlying TCP connection is closed. Components https://github.com/libp2p/rust-yamux/blob/yamux-v0.13.1/yamux/src/connection.rs#L289 DetailsThis attack is inspired by the HTTP/2 Rapid Reset Attack (CVE 2023-44487), HTTP/2 Ping Flood (CVE-2019-9512), and the QUIC Path Validation attack (see my blog post: https://seemann.io/posts/2023-12-18-exploiting-quics-path-validation/). ImpactAn attacker can cause a remote node to run out of memory, which will result in the corresponding process getting terminated by the operating system. Depending on the application protocols running on top of rust-libp2p, higher amplification factors are possible. For example, image a protocol that sends out 10 MB of data as a result of an incoming request. By issuing that request and sending a Yamux stream window update (together ~100-200 bytes), the victim would now enqueue the entire 10 MB into its frame buffer. Any block transfer / sync protocols might be good candidates. In addition to consuming huge amounts of memory, this attack also drives up the victim's CPU load, such that the allocation of memory at some point becomes CPU-limited. This was originally submitted by @marteen-seemann to the Ethereum Foundation bug bounty program. Fixed in
0.13.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.13.0
unknown
Dependencies (8)
|
|
0.12.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.12.1
unknown
Dependencies (9)
+ 1 more |
|
0.12.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.12.0
unknown
Dependencies (8)
|
|
0.11.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.11.1
unknown
Dependencies (16)
+ 8 more |
|
0.11.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.11.0
unknown
Dependencies (14)
+ 6 more |
|
0.10.2
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.10.2
unknown
Dependencies (14)
+ 6 more |
|
0.10.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.10.1
unknown
Dependencies (14)
+ 6 more |
|
0.10.1-rc.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.10.1-rc.1
unknown
Dependencies (14)
+ 6 more |
|
0.10.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.10.0
unknown
Dependencies (14)
+ 6 more |
|
0.8.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.8.1
unknown
Dependencies (12)
+ 4 more |
|
0.9.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.9.0
unknown
Dependencies (14)
+ 6 more |
|
0.8.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.8.0
unknown
Dependencies (12)
+ 4 more |
|
0.7.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.7.0
unknown
Dependencies (12)
+ 4 more |
|
0.6.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.6.0
unknown
Dependencies (12)
+ 4 more |
|
0.5.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.5.0
unknown
Dependencies (12)
+ 4 more |
|
0.4.9
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.9
unknown
Dependencies (12)
+ 4 more |
|
0.4.8
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.8
unknown
Dependencies (12)
+ 4 more |
|
0.4.7
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.7
unknown
Dependencies (12)
+ 4 more |
|
0.4.6
unknown
yanked
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.6
unknown
yanked
Dependencies (12)
+ 4 more |
|
0.4.5
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.5
unknown
Dependencies (11)
+ 3 more |
|
0.4.4
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.4
unknown
Dependencies (11)
+ 3 more |
|
0.4.3
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.3
unknown
Dependencies (11)
+ 3 more |
|
0.4.2
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.2
unknown
Dependencies (11)
+ 3 more |
|
0.4.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.1
unknown
Dependencies (11)
+ 3 more |
|
0.4.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.4.0
unknown
Dependencies (11)
+ 3 more |
|
0.3.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.3.0
unknown
Dependencies (11)
+ 3 more |
|
0.2.2
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.2.2
unknown
Dependencies (13)
+ 5 more |
|
0.2.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.2.1
unknown
Dependencies (13)
+ 5 more |
|
0.2.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.2.0
unknown
Dependencies (11)
+ 3 more |
|
0.1.9
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.9
unknown
Dependencies (11)
+ 3 more |
|
0.1.8
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.8
unknown
Dependencies (11)
+ 3 more |
|
0.1.7
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.7
unknown
Dependencies (11)
+ 3 more |
|
0.1.6
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.6
unknown
Dependencies (13)
+ 5 more |
|
0.1.5
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.5
unknown
Dependencies (12)
+ 4 more |
|
0.1.4
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.4
unknown
Dependencies (12)
+ 4 more |
|
0.1.3
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.3
unknown
Dependencies (12)
+ 4 more |
|
0.1.2
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.2
unknown
Dependencies (12)
+ 4 more |
|
0.1.1
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.1
unknown
Dependencies (12)
+ 4 more |
|
0.1.0
unknown
1 CVE
CVE-2026-32314
GHSA-vxx9-2994-q338
Mar 13, 2026
Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145
High
Network
Low
None
None
SummaryThe 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 ScenarioAn 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:
PatchesUsers should upgrade to This vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program Fixed in
0.13.10
References Updated Mar 16, 2026 · Source: OSV.dev |
0.1.0
unknown
Dependencies (12)
+ 4 more |