CVE-2026-34063: CWE-617: Reachable Assertion in nimiq network-libp2p
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.
AI Analysis
Technical Summary
Nimiq's network-libp2p prior to v1.3.0 uses a libp2p ConnectionHandler state machine for discovery that assumes a maximum of one inbound and one outbound discovery substream per connection. If a remote peer opens or negotiates a second discovery protocol substream on the same connection, the handler triggers a panic via reachable assertions ('Inbound already connected' or 'Outbound already connected'). This panic causes the networking task (swarm) to crash, resulting in the node's p2p networking going offline until a restart occurs. The vulnerability is tracked as CWE-617 (Reachable Assertion). The issue was fixed in network-libp2p version 1.3.0. No known mitigations or workarounds exist besides upgrading.
Potential Impact
This vulnerability causes a denial of service by crashing the networking task of the node, rendering the p2p networking offline until manual restart. There is no impact on confidentiality or integrity. The CVSS v3.1 base score is 7.5 (High) reflecting network attack vector, low complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact.
Mitigation Recommendations
A fix for this vulnerability is available in network-libp2p version 1.3.0. Users should upgrade to version 1.3.0 or later to remediate this issue. No workarounds are known. Since this is not a cloud service, remediation depends on applying the patch. Patch status is confirmed by the vendor's release notes indicating the fix in v1.3.0.
CVE-2026-34063: CWE-617: Reachable Assertion in nimiq network-libp2p
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Nimiq's network-libp2p prior to v1.3.0 uses a libp2p ConnectionHandler state machine for discovery that assumes a maximum of one inbound and one outbound discovery substream per connection. If a remote peer opens or negotiates a second discovery protocol substream on the same connection, the handler triggers a panic via reachable assertions ('Inbound already connected' or 'Outbound already connected'). This panic causes the networking task (swarm) to crash, resulting in the node's p2p networking going offline until a restart occurs. The vulnerability is tracked as CWE-617 (Reachable Assertion). The issue was fixed in network-libp2p version 1.3.0. No known mitigations or workarounds exist besides upgrading.
Potential Impact
This vulnerability causes a denial of service by crashing the networking task of the node, rendering the p2p networking offline until manual restart. There is no impact on confidentiality or integrity. The CVSS v3.1 base score is 7.5 (High) reflecting network attack vector, low complexity, no privileges required, no user interaction, unchanged scope, no confidentiality or integrity impact, and high availability impact.
Mitigation Recommendations
A fix for this vulnerability is available in network-libp2p version 1.3.0. Users should upgrade to version 1.3.0 or later to remediate this issue. No workarounds are known. Since this is not a cloud service, remediation depends on applying the patch. Patch status is confirmed by the vendor's release notes indicating the fix in v1.3.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-25T16:21:40.866Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e9290319fe3cd2cde95599
Added to database: 4/22/2026, 8:01:07 PM
Last enriched: 4/22/2026, 8:16:10 PM
Last updated: 4/22/2026, 11:39:46 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.