Description
Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p` discovery uses a libp2p `ConnectionHandler` 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 `panic!(\"Inbound already connected\")` / `panic!(\"Outbound already connected\")` 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.
Affected products
nimiq: nimiq proof-of-stake
References4
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74h… PatchVendor Advisory
- github.com/nimiq/core-rs-albatross/commit/e0d4e01994f061bf41d3c… Patch
- github.com/nimiq/core-rs-albatross/pull/3666 Issue TrackingPatch
- github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0 Release Notes
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 29 · as of 13 November 2026
- CWE
- CWE-617
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.