{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-consensus. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34069 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34069 is a medium-severity vulnerability in nimiq core-rs-albatross, published on 13 Apr 2026."},"fix_prompt":"Check this codebase for CVE-2026-34069 and fix it if it is affected.\n\nWhat it is: CVE-2026-34069 is a medium-severity vulnerability in nimiq core-rs-albatross, published on 13 Apr 2026. \nExploitation: There is no known exploitation of CVE-2026-34069 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-consensus (crates.io): affected all versions up to 1.2.2; no fix listed\n- nimiq-consensus (crates.io): affected all versions up to 1.2.2; 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-34069/ (Markdown: https://insights.sbomify.com/CVE-2026-34069/index.md)","id":"CVE-2026-34069","markdown":"https://insights.sbomify.com/CVE-2026-34069/index.md","name":"CVE-2026-34069","record":{"aliases":["GHSA-48m6-486p-9j8p"],"analysis":null,"analysis_generated_by":null,"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-617","name":"Reachable Assertion"}],"description":"nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. In versions 1.2.2 and below, an unauthenticated p2p peer can cause the RequestMacroChain message handler task to panic. Sending a RequestMacroChain message where the first locator hash on the victim’s main chain is a micro block hash (not a macro block hash) causes said panic. The RequestMacroChain::handle handler selects the locator based only on \"is on main chain\", then calls get_macro_blocks() and panics via .unwrap() when the selected hash is not a macro block (BlockchainError::BlockIsNotMacro). This issue has been fixed in version 1.3.0.","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-consensus panics via RequestMacroChain micro-block locator","id":"CVE-2026-34069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"LangChain Core has Path Traversal vulnerabilites in legacy `load_prompt` functions","id":"CVE-2026-34070"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.2.2"],"package":"nimiq-consensus","purl":null,"source":"GHSA-48m6-486p-9j8p"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.2.2"],"package":"nimiq-consensus","purl":"pkg:cargo/nimiq-consensus","source":"GHSA-48m6-486p-9j8p"}],"prev":{"headline":"nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge","id":"CVE-2026-34068"},"products":["core-rs-albatross"],"published":"2026-04-13","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-14","vendors":["nimiq"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-34069/"}