{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-primitives.","exploited":"There is no known exploitation of CVE-2026-54542 in the wild and no public exploit code.","fix":"Upgrade nimiq-primitives to 1.6.0 or later.","what":"CVE-2026-54542 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-54542 and fix it if it is affected.\n\nWhat it is: CVE-2026-54542 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-54542 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-54542/ (Markdown: https://insights.sbomify.com/CVE-2026-54542/index.md)","id":"CVE-2026-54542","markdown":"https://insights.sbomify.com/CVE-2026-54542/index.md","name":"CVE-2026-54542","record":{"aliases":["GHSA-5rg2-xv9j-gv5p"],"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 sync peer can crash a Nimiq node by sending a crafted TrieChunk, causing an out-of-bounds panic during state synchronization.","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-125","name":"Out-of-bounds Read"}],"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 whose proof contains a TrieNodeChild suffix that is individually valid but exceeds the 63-byte KeyNibbles backing array when combined with the parent key. KeyNibbles::Add in primitives/src/key_nibbles.rs performs the combined slice operation without checking the total length, and the input reaches put_chunk, TrieNodeChild::key, and TrieNodeChild::is_stump before proof.verify, so the attacker does not need a valid cryptographic proof. Exploitation requires the attacker to be selected as the victim's sync peer during state sync. The resulting out-of-bounds 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: Out-of-bounds panic in KeyNibbles::Add from oversized child suffix in a deserialized proof","id":"CVE-2026-54542","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":"Froxlor DomainZones.add allows DNS zone-file RR injection via record/type fields","id":"CVE-2026-54543"},"packages":[{"ecosystem":"crates.io","fixed":["1.6.0"],"introduced":["0"],"last_affected":[],"package":"nimiq-primitives","purl":null,"source":"GHSA-5rg2-xv9j-gv5p"},{"ecosystem":"crates.io","fixed":["1.6.0"],"introduced":["0"],"last_affected":[],"package":"nimiq-primitives","purl":"pkg:cargo/nimiq-primitives","source":"GHSA-5rg2-xv9j-gv5p"}],"prev":{"headline":"Nimiq: Panic in TrieProof::verify via child_index unwrap on equal-length keys","id":"CVE-2026-54541"},"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-14","vendors":["nimiq"]},"summary":"A malicious sync peer can crash a Nimiq node by sending a crafted TrieChunk, causing an out-of-bounds panic during state synchronization.","url":"https://insights.sbomify.com/CVE-2026-54542/"}