{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-primitives.","exploited":"There is no known exploitation of CVE-2026-54541 in the wild and no public exploit code.","fix":"Upgrade nimiq-primitives to 1.6.0 or later.","what":"CVE-2026-54541 is a low-severity denial of service vulnerability in nimiq core-rs-albatross, published on 14 Sep 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-54541 and fix it if it is affected.\n\nWhat it is: CVE-2026-54541 is a low-severity denial of service vulnerability in nimiq core-rs-albatross, published on 14 Sep 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-54541 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-primitives (crates.io): affected all versions; fixed in 1.6.0\n- nimiq-primitives (crates.io): affected all versions; fixed in 1.6.0\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-54541/ (Markdown: https://insights.sbomify.com/CVE-2026-54541/index.md)","id":"CVE-2026-54541","markdown":"https://insights.sbomify.com/CVE-2026-54541/index.md","name":"CVE-2026-54541","record":{"aliases":["GHSA-46wq-28cx-mhw4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Nimiq blockchain node","requires_auth":"none","summary":"A malicious peer can crash a syncing Nimiq node by sending crafted trie proofs, causing a panic via an unwrap on equal-length keys.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to 1.6.0, a malicious state-sync peer can crash a syncing node by sending a crafted TrieChunk proof containing two TrieProofNode values with identical keys. TrieProof::verify calls TrieProofNode::child_index in primitives/src/trie/trie_proof_node.rs, where is_prefix_of accepts equal keys and KeyNibbles::get is called at the key length, returns None, and is unconditionally unwrapped. Untrusted ResponseChunk data reaches commit_chunks, put_chunk, and proof.verify before cryptographic proof validation, so the attacker does not need a valid proof. Exploitation requires the attacker to be selected as the victim's sync peer during state sync, and the resulting panic is transient because the node restarts and resynchronizes. This issue is fixed in version 1.6.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":true,"headline":"Nimiq: Panic in TrieProof::verify via child_index unwrap on equal-length keys","id":"CVE-2026-54541","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: Out-of-bounds panic in KeyNibbles::Add from oversized child suffix in a deserialized proof","id":"CVE-2026-54542"},"packages":[{"ecosystem":"crates.io","fixed":["1.6.0"],"introduced":["0"],"last_affected":[],"package":"nimiq-primitives","purl":null,"source":"GHSA-46wq-28cx-mhw4"},{"ecosystem":"crates.io","fixed":["1.6.0"],"introduced":["0"],"last_affected":[],"package":"nimiq-primitives","purl":"pkg:cargo/nimiq-primitives","source":"GHSA-46wq-28cx-mhw4"}],"prev":{"headline":"Authenticated terminal command whitelist bypass in Pheditor","id":"CVE-2026-54540"},"products":["core-rs-albatross"],"published":"2026-09-14","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-09-16","vendors":["nimiq"]},"summary":"A malicious peer can crash a syncing Nimiq node by sending crafted trie proofs, causing a panic via an unwrap on equal-length keys.","url":"https://insights.sbomify.com/CVE-2026-54541/"}