CVE-2026-34062: nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request`…
CVE-2026-34062 · Severity: medium · CVSS 5.3 · Published 2026-04-22
nimiq-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `MessageCodec::read_request` and `read_response` call `read_to_end()` on inbound substreams, so a remote peer can send only a partial frame and keep the substream open. because `Behaviour::new` also sets `with_max_concurrent_streams(1000)`, the node exposes a much larger stalled-slot budget than the library default. The patch for this vulnerability is formally released as part of v1.3.0. No known workarounds are available.
No. Junglewise Threat Intelligence has no report of CVE-2026-34062 being exploited in the wild.
How severe is CVE-2026-34062?
Medium severity, with a CVSS score of 5.3, published 22 April 2026.
Which products and versions are affected?
Nimiq Proof-Of-Stake. The advisory does not name versions.
Is there a fix for CVE-2026-34062?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-34062?
Check whether you run Nimiq Proof-Of-Stake. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.