CVE-2026-54541
LOWDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 20% of all known CVEs.
References
Related Vulnerabilities
Other CWE-248 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-59538 | High | 7.5 | 8.9% | - | Fix |
| CVE-2025-53366 | High | 8.7 | 7.3% | - | - |
| CVE-2021-37714 | High | 7.5 | 6.9% | - | Fix |
| CVE-2018-11466 | Critical | 9.8 | 4.0% | - | - |
| CVE-2025-59465 | High | 7.5 | 3.8% | - | Fix |
| CVE-2018-7852 | High | 7.5 | 3.6% | - | - |
Common questions
How do I fix CVE-2026-54541?
No published fix for CVE-2026-54541 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-54541 being actively exploited?
Not that we know of. CVE-2026-54541 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.27% is the estimated probability that it will be exploited in the next 30 days. That is higher than 20% of all scored CVEs.
How severe is CVE-2026-54541?
CVE-2026-54541 has a CVSS v3 base score of 3.7, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-54541
Markdown
[](https://tridentstack.com/cve/CVE-2026-54541)HTML
<a href="https://tridentstack.com/cve/CVE-2026-54541"><img src="https://tridentstack.com/cve/badge/CVE-2026-54541.svg" alt="CVE-2026-54541"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-16.