{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-blockchain. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34066 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34066 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34066 is a medium-severity denial of service vulnerability in nimiq-blockchain, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-34066 and fix it if it is affected.\n\nWhat it is: CVE-2026-34066 is a medium-severity denial of service vulnerability in nimiq-blockchain, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-34066 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-blockchain (crates.io): affected all versions up to 0.2.0; no fix listed\n- nimiq-blockchain (crates.io): affected all versions up to 0.2.0; no fix listed\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-34066/ (Markdown: https://insights.sbomify.com/CVE-2026-34066/index.md)","id":"CVE-2026-34066","markdown":"https://insights.sbomify.com/CVE-2026-34066/index.md","name":"CVE-2026-34066","record":{"aliases":["GHSA-j99g-7rqw-q9jg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust blockchain library","requires_auth":"none","summary":"A remote peer can trigger a panic in the nimiq-blockchain library during history sync, causing a denial of service.","user_interaction":"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:H/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"},{"id":"CWE-617","name":"Reachable Assertion"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: \u0026[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.","ecosystems":["crates.io"],"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-blockchain: Peer-triggerable panic during history sync","id":"CVE-2026-34066","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"nimiq-transaction vulnerable to panic via `HistoryTreeProof` length mismatch","id":"CVE-2026-34067"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-blockchain","purl":null,"source":"GHSA-j99g-7rqw-q9jg"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-blockchain","purl":"pkg:cargo/nimiq-blockchain","source":"GHSA-j99g-7rqw-q9jg"}],"prev":{"headline":"nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals","id":"CVE-2026-34065"},"products":["nimiq-blockchain"],"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["nimiq"]},"summary":"A remote peer can trigger a panic in the nimiq-blockchain library during history sync, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-34066/"}