Transient node crash via duplicate trie-proof keys
Published Sep 14, 2026 · Updated Sep 14, 2026
Uncaught exception in Nimiq core-rs-albatross before 1.6.0 allows remote attackers to crash a syncing node via a crafted TrieChunk proof. TrieProofNode::child_index treats an equal-length key as a prefix, reads a nibble at the key length, and unwraps the resulting None. The attacker must be chosen as the state-sync peer; no valid proof is required, and the transient panic ends when the node restarts and resynchronizes.
Summary
What happened
Uncaught exception in Nimiq core-rs-albatross before 1.6.0 allows remote attackers to crash a syncing node via a crafted TrieChunk proof. TrieProofNode::child_index treats an equal-length key as a prefix, reads a nibble at the key length, and unwraps the resulting None. The attacker must be chosen as the state-sync peer; no valid proof is required, and the transient panic ends when the node restarts and resynchronizes.
The record
- CVE
- CVE-2026-54541
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Nimiq
- Product
- core-rs-albatross
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo