Network Libp2P
Approved changes feed: RSS · Atom
cpe:2.3:a:nimiq:network-libp2p:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Nimiq (a6c6d398-2780-5e77-a82f-ca37478d870d) |
|---|---|
| Product | Network Libp2P (b4b600b5-7c9f-5b5a-a0fa-fb43a54a86a1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-34063 |
vulnerable | 2026-06-08 07:59:11.726380 |
network-libp2p: Peer can crash the node by opening discovery protocol substream twice
HIGH (7.5)
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.
Published: 2026-04-22T19:40:26.837Z
Updated: 2026-04-23T13:54:06.421Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34062 |
vulnerable | 2026-06-08 07:59:11.725915 |
Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/response
MEDIUM (5.3)
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.
Published: 2026-04-22T19:23:36.838Z
Updated: 2026-04-23T12:57:42.075Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.