CVE-2026-40092
HighSummary
In versions 1.3.0 and below, a malicious network peer can crash any Nimiq full node by publishing a crafted Kademlia DHT record. The crafted record contains a signature field with a byte length not equal to 64, leading to a panic during verification.
Risk Assessment
The organization may experience service outages related to Nimiq, potentially resulting in loss of availability and user trust. Malicious attacks can be executed by unauthorized network participants.
Recommendation
It is recommended to upgrade to version 1.4.0 or later to mitigate this vulnerability. Monitoring and securing nodes against malicious activities is also advisable.
Original NVD description (English source)
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In versions 1.3.0 and below, a malicious network peer can crash any Nimiq full node by publishing a crafted Kademlia DHT record. The maliciously crafted record would contain a TaggedSigned<ValidatorRecord, KeyPair> with a signature field whose byte length is not exactly 64 in order to cause a crash. When the victim node's DHT verifier calls TaggedSigned::verify, execution reaches Ed25519Signature::from_bytes(sig).unwrap() in the TaggedPublicKey implementation for Ed25519PublicKey. The from_bytes call fails because ed25519_zebra::Signature::try_from rejects slices not 64 bytes, and the unwrap() panics. The BLS TaggedPublicKey implementation correctly returns false on error; only the Ed25519 implementation panics. This issue has been fixed in version 1.4.0.