Protocol vulnerabilities
We track 9 vulnerabilities in Protocol products across 3 products. 9 are rated high or critical, and none are known to be exploited. The most recent was published on April 7, 2026.
Latest Protocol vulnerabilities
- 8.2 High severity
rust-libp2p: Allocation of Resources Without Limits or Throttling
libp2p-rust is the official rust language Implementation of the libp2p networking stack. Prior to 0.17.1, the rendezvous server stores pagination cookies without bounds. An unauthenticated peer can repeatedly issue DISCOVER requests and force unbounded memory
- 7.5 High severity
rust-libp2p: Allocation of Resources Without Limits or Throttling
libp2p-rust is the official rust language Implementation of the libp2p networking stack. Prior to 0.17.1, libp2p-rendezvous server has no limit on how many namespaces a single peer can register. A malicious peer can just keep registering unique namespaces in a
- 7.5 High severity
rust-libp2p: Integer Overflow or Wraparound
libp2p-rust is the official rust language Implementation of the libp2p networking stack. In versions prior to 0.49.3, the Gossipsub implementation accepts attacker-controlled PRUNE backoff values and may perform unchecked time arithmetic when storing backoff s
- 7.5 High severity
rust-yamux: Uncaught Exception
Yamux is a stream multiplexer over reliable, ordered connections such as TCP/IP. Prior to 0.13.10, 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. 26
- 7.5 High severity
rust-yamux: Integer Overflow or Wraparound
Yamux is a stream multiplexer over reliable, ordered connections such as TCP/IP. From 0.13.0 to before 0.13.9, a specially crafted WindowUpdate can cause arithmetic overflow in send-window accounting, which triggers a panic in the connection state machine. Thi
- 7.5 High severity
go-libp2p: Uncontrolled Resource Consumption
libp2p is a networking stack and library modularized out of The IPFS Project, and bundled separately for other tools to use. In go-libp2p, by using signed peer records a malicious actor can store an arbitrary amount of data in a remote node’s memory. This memo
- 7.5 High severity
go-libp2p: Allocation of Resources Without Limits or Throttling
go-libp2p is the offical libp2p implementation in the Go programming language. Version `0.18.0` and older of go-libp2p are vulnerable to targeted resource exhaustion attacks. These attacks target libp2p’s connection, stream, peer, and memory management. An att
- 7.5 High severity
js-libp2p: Allocation of Resources Without Limits or Throttling
js-libp2p is the official javascript Implementation of libp2p networking stack. Versions older than `v0.38.0` of js-libp2p are vulnerable to targeted resource exhaustion attacks. These attacks target libp2p’s connection, stream, peer, and memory management. An
- 7.5 High severity
rust-libp2p: Allocation of Resources Without Limits or Throttling
libp2p-rust is the official rust language Implementation of the libp2p networking stack. In versions prior to 0.45.1 an attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process r