{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34063 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34063 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34063 is a high-severity vulnerability in nimiq network-libp2p, published on 22 Apr 2026."},"fix_prompt":"Check this codebase for CVE-2026-34063 and fix it if it is affected.\n\nWhat it is: CVE-2026-34063 is a high-severity vulnerability in nimiq network-libp2p, published on 22 Apr 2026. \nExploitation: There is no known exploitation of CVE-2026-34063 in the wild and no public exploit code.\n\nAffected product: nimiq network-libp2p. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34063/ (Markdown: https://insights.sbomify.com/CVE-2026-34063/index.md)","id":"CVE-2026-34063","markdown":"https://insights.sbomify.com/CVE-2026-34063/index.md","name":"CVE-2026-34063","record":{"aliases":["GHSA-74hp-mhfx-m45h"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"nimiq_proof-of-stake","vendor":"nimiq"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"network-libp2p: Peer can crash the node by opening discovery protocol substream twice","id":"CVE-2026-34063","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"nimiq-account: Vesting insufficient funds error can panic","id":"CVE-2026-34064"},"packages":[],"prev":{"headline":"Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/response","id":"CVE-2026-34062"},"products":["network-libp2p"],"published":"2026-04-22","related":[{"cvss_score":9.6,"headline":"nimiq-block has skip block quorum bypass via out-of-range BitSet indices \u0026 u16 truncation","id":"CVE-2026-33471","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.1,"headline":"nimiq-blockchain is missing a wall-clock upper bound on block timestamps","id":"CVE-2026-40093","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":7.5,"headline":"nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals","id":"CVE-2026-34065","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.5,"headline":"Nimiq: Remote crash via off-by-one signer bounds check in proposal buffer","id":"CVE-2026-32605","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":7.5,"headline":"nimiq/core-rs-albatross: Discovery handshake limit could underflow and later provoke a deterministic overflow panic","id":"CVE-2026-33184","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":7.1,"headline":"nimiq/core-rs-albatross's nimiq-blockchain missing proposal body root verification","id":"CVE-2026-28402","kev_date_added":null,"published":"2026-02-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["nimiq"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-34063/"}