{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34062 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34062 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34062 is a medium-severity denial of service vulnerability in nimiq network-libp2p, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34062 and fix it if it is affected.\n\nWhat it is: CVE-2026-34062 is a medium-severity denial of service vulnerability in nimiq network-libp2p, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34062 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-34062/ (Markdown: https://insights.sbomify.com/CVE-2026-34062/index.md)","id":"CVE-2026-34062","markdown":"https://insights.sbomify.com/CVE-2026-34062/index.md","name":"CVE-2026-34062","record":{"aliases":["GHSA-gh7r-qh4p-q4fr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Nimiq libp2p library","requires_auth":"none","summary":"A remote peer can exhaust resources by keeping substreams open, causing denial of service in Nimiq libp2p nodes.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nimiq_proof-of-stake","vendor":"nimiq"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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.","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":"Nimiq has Allocation of Resources Without Limits or Throttling in its libp2p request/response","id":"CVE-2026-34062","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"network-libp2p: Peer can crash the node by opening discovery protocol substream twice","id":"CVE-2026-34063"},"packages":[],"prev":{"headline":"nimiq/core-rs-albatross: Macro block proposal interlink bug","id":"CVE-2026-34061"},"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":"network-libp2p: Peer can crash the node by opening discovery protocol substream twice","id":"CVE-2026-34063","kev_date_added":null,"published":"2026-04-22"},{"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":"A remote peer can exhaust resources by keeping substreams open, causing denial of service in Nimiq libp2p nodes.","url":"https://insights.sbomify.com/CVE-2026-34062/"}