CVE Tools
Track your stack

CVE-2026-32314

Yamux remote Panic via malformed Data frame with SYN set and len = 262145

No known exploitation. EPSS puts it in the 48th percentile. Fixed in 0.13.10.

CVSS 3.17.5HighEPSS percentile48th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix0.13.10Upgrade to this build

Published Updated Sources: CVE.org, NVD, GitHub, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Libp2p Rust-yamuxAffected: < 0.13.10Upgrade to: not statedStated by: CVE record
  • Crates.io YamuxAffected: < 0.13.10Upgrade to: 0.13.10Stated by: GitHub advisory
  • Protocol YamuxAffected: < 0.13.10Upgrade to: 0.13.10Stated by: NVD
  • Сообщество свободного программного обеспечения YamuxAffected: 0.13.9Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Yamux vulnerable to remote Panic via malformed Data frame with SYN set and len = 262145

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS48th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 6 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Publishedweakness classified

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Yamux, not every advisory.