Skip to main content
VulnerabilityPublished

CVE-2026-34063: nimiq network-libp2p · Reachable Assertion

Affects nimiq network-libp2pSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.3.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade network-libp2p and nimiq/network-libp2p to 1.3.0.

Affected software

ProductAffectedFixed in
nimiqnetwork-libp2pAffected
  • <1.3.0
Fixed in
  • 1.3.0
GitHubnimiq/network-libp2ppkg:github/nimiq/network-libp2pOther threatsAffected
  • <1.3.0
Fixed in
  • 1.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to network-libp2p version 1.3.0 or later where the vulnerability is patched. No known workarounds exist. Since this is not a cloud service, remediation depends on applying the official fix.

Description

A reachable assertion vulnerability exists in Nimiq's network-libp2p prior to version 1.3.0. The network-libp2p discovery protocol handler incorrectly assumes only one inbound and one outbound discovery substream per connection. If a remote peer opens a second discovery substream on the same connection, the handler triggers a panic, causing the networking task to crash and the node's p2p networking to go offline until restarted. This denial-of-service condition affects availability but does not impact confidentiality or integrity. The issue is fixed in version 1.3.0. No known workarounds are available.

References

Community reviews

Loading reviews…