CVE-2026-32314: Yamux Yamux Vulnerable To Remote Panic Vulnerability

HIGH
Advisory Identifier: GHSA-vxx9-2994-q338
Share
CWE-617 CWE-248
Published
Advisory Summary

CVE-2026-32314 is a HIGH yamux vulnerable to remote panic vulnerability (CWE-617: Reachable Assertion) affecting Yamux libraries in the crates.io ecosystem. The issue involves yamux vulnerable to remote panic via malformed data frame with syn set and len = 262145. Remediation is available by upgrading affected packages to version 0.13.10.

CVE-2026-32314 at a Glance

CVE Identifier CVE-2026-32314
GHSA Identifier GHSA-vxx9-2994-q338
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-617: Reachable Assertion
Affected Product Yamux
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2026-32314

To remediate this vulnerability, upgrade all affected Yamux dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

yamux fixed: 0.13.10 
Upgrade yamux to 0.13.10
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for yamux

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-32314, inspect your project dependencies for Yamux:

inspect dependencies for yamux

Analyze the terminal output to locate any version of Yamux in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.13.10), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-617: Reachable Assertion, where the product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. In Yamux, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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: 1. Establish a standard authenticated transport session that negotiates Yamux. 2. Send one Yamux frame with: - Tag = Data - Flags = SYN - StreamId = 1 (or any new inbound stream id) - Length = DEFAULT_CREDIT + 1 (e.g. 262145) - Body of matching size 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

CVE-2026-32314 Affected Yamux Versions

1 component(s)
Fixed Versions:
0.13.10
Product / Package Ecosystem Affected Versions Fixed Version
yamux
 crates.io
< 0.13.10
0.13.10

References

GitHub Advisory / Wiki ADVISORY
https://github.com/libp2p/rust-yamux/security/advisories/GHSA-vxx9-2994-q338
NVD — CVE-2026-32314 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-32314
Yamux Source Repository REPOSITORY
https://github.com/libp2p/rust-yamux

Frequently Asked Questions

What is CVE-2026-32314?
CVE-2026-32314 is a security vulnerability in Yamux involving Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145 under CWE-617: Reachable Assertion.
Which Yamux versions are affected?
Affected versions include releases prior to 0.13.10 across affected packages: yamux.
What version fixes CVE-2026-32314?
Upgrading to 0.13.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is yamux affected?
Yes, yamux is affected in releases prior to 0.13.10. Upgrade your dependency to 0.13.10 or later.
What CWE is associated with CVE-2026-32314?
CVE-2026-32314 is classified under CWE-617: Reachable Assertion (The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.).
How can I check crates.io dependencies for CVE-2026-32314?
Run the dependency tree command: 'inspect dependencies for yamux'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vxx9-2994-q338",
  "modified" : "2026-03-16T22:01:11Z",
  "published" : "2026-03-13T20:04:38Z",
  "aliases" : [ "CVE-2026-32314" ],
  "summary" : "Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145",
  "details" : "### Summary\nThe 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).\nOn 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.\nThis is remotely reachable over a normal Yamux session and does not require authentication. kind of vulnerability is it? Who is \n#### Attack Scenario  \nAn 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:\n1. Establish a standard authenticated transport session that negotiates Yamux.\n2. Send one Yamux frame with:\n   - Tag = Data\n   - Flags = SYN\n   - StreamId = 1 (or any new inbound stream id)\n   - Length = DEFAULT_CREDIT + 1 (e.g. 262145)\n   - Body of matching size\nThis can trigger a panic (stream not found) and terminate the process, depending on host application panic policy.\n### Patches\nUsers should upgrade to `yamux` `v0.13.10`\n\nThis vulnerability was originally submitted by @revofusion to the Ethereum Foundation bug bounty program",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "yamux"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.13.10"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/libp2p/rust-yamux/security/advisories/GHSA-vxx9-2994-q338"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32314"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/libp2p/rust-yamux"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-248", "CWE-617" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-13T20:04:38Z",
    "nvd_published_at" : "2026-03-16T14:19:34Z"
  }
}