CVE-2026-46541: nimiq core-rs-albatross · Unchecked Error Condition
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 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% 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 9 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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
A fix is available in Nimiq core-rs-albatross version 1.4.0. Users should upgrade to version 1.4.0 or later to remediate this vulnerability. No other mitigation guidance is provided or required.
Description
Nimiq is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.4.0, iIn handle_dht_get(), the DhtResults accumulator is only initialized when the first DHT record passes verification. If the first record fails (from a malicious DHT node), DhtResults is never created, and all subsequent valid records are discarded with "DHT inconsistent state" errors. This issue has been patched in version 1.4.0.