CVE-2026-34063
Nimiq's network-libp2p is a Nimiq network implementation based on libp2p.
Published Apr 22, 2026 · updated Jun 17, 2026 · nimiq nimiq proof-of-stake
Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, discovery uses a libp2p state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a / path instead of failing closed. This causes a remote crash of the networking task (swarm), taking the node's p2p networking offline until restart. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Apr 22, 2026 · NIST NVD
Detected
Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, discovery uses a libp2p state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a / path instead of failing closed. This
Jun 17, 2026 · NIST NVD
Updated
Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, discovery uses a libp2p state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a remote peer opens/negotiate the discovery protocol substream a second time on the same connection, the handler hits a / path instead of failing closed. This
Affected
- cpe nimiq/nimiq proof-of-stakeversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-34063
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2026-34063
Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, discovery uses a libp2p state machine. the handler assumes there is at most one inbound and one outbound discovery substream per connection. if a
nvd.nist.gov