{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-primitives.","exploited":"There is no known exploitation of CVE-2026-46539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46539 is a medium-severity vulnerability in nimiq core-rs-albatross, published on 9 Jun 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-46539 and fix it if it is affected.\n\nWhat it is: CVE-2026-46539 is a medium-severity vulnerability in nimiq core-rs-albatross, published on 9 Jun 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-46539 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-primitives (crates.io): affected all versions up to 0.2.0; no fix listed\n- nimiq-primitives (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-46539/ (Markdown: https://insights.sbomify.com/CVE-2026-46539/index.md)","id":"CVE-2026-46539","markdown":"https://insights.sbomify.com/CVE-2026-46539/index.md","name":"CVE-2026-46539","record":{"aliases":["GHSA-799f-29jm-gr6c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust blockchain library","requires_auth":"none","summary":"Attackers can forge block inclusion proofs by exploiting a logic flaw that skips verification when hop lists are empty, affecting Nimiq core-rs-albatross users.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.4.0, a logic flaw in BlockInclusionProof::is_block_proven causes the function to return true without performing any cryptographic verification when get_interlink_hops yields an empty hop list. This occurs when the target block is at the election block position immediately preceding the election head's epoch. An attacker providing transaction inclusion proofs can forge a MacroBlock header for that epoch position and have it accepted as \"proven\" without any hash or signature verification. This issue has been patched in version 1.4.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-primitives: BlockInclusionProof interlink issue when hops are empty","id":"CVE-2026-46539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Nimiq light-blockchain: Light blockchain rebranch issue","id":"CVE-2026-46540"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-primitives","purl":null,"source":"GHSA-799f-29jm-gr6c"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-primitives","purl":"pkg:cargo/nimiq-primitives","source":"GHSA-799f-29jm-gr6c"}],"prev":{"headline":"Microsoft UFO accepts cross-device TASK_END messages by session_id only, allowing peer task-result injection","id":"CVE-2026-46538"},"products":["core-rs-albatross"],"published":"2026-06-09","related":[],"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":"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-06-10","vendors":["nimiq"]},"summary":"Attackers can forge block inclusion proofs by exploiting a logic flaw that skips verification when hop lists are empty, affecting Nimiq core-rs-albatross users.","url":"https://insights.sbomify.com/CVE-2026-46539/"}