CVE-2026-40092: nimiq core-rs-albatross · Unchecked Return Value
Affects nimiq core-rs-albatrossSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.4.0 soon.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade core-rs-albatross and github/nimiq/core-rs-albatross to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nimiqcore-rs-albatross | Affected
| Fixed in
|
crates.iogithub/nimiq/core-rs-albatrosspkg:cargo/github/nimiq/core-rs-albatrossOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to nimiq core-rs-albatross version 1.4.0 or later, where this issue has been fixed. Patch status is not explicitly stated in the vendor advisory, but the fix is included in version 1.4.0. Until upgraded, nodes remain vulnerable to denial-of-service via crafted DHT records.
Description
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.
References
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-27w2-87xv-37c6 (opens in a new tab)
- github.com/nimiq/core-rs-albatross/pull/3708 (opens in a new tab)
- github.com/nimiq/core-rs-albatross/commit/807ee8e99a7ccdc604d49971f292854bfa36754d (opens in a new tab)
- github.com/nimiq/core-rs-albatross/releases/tag/v1.4.0 (opens in a new tab)