CVE-2026-34061: nimiq core-rs-albatross · Insufficient Verification of Data Authenticity
Affects nimiq core-rs-albatrossSource CVE Database V5
Not known to be exploited · CVSS 4.9 Medium : upgrade to 1.3.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.3.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 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.3.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.3.0 or later, where this vulnerability has been patched. Since the vendor advisory indicates the issue is fixed in version 1.3.0, applying this official fix is the recommended remediation. No additional mitigation steps are indicated.
Description
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, an elected validator proposer can send an election macro block whose header.interlink does not match the canonical next interlink. Honest validators accept that proposal in verify_macro_block_proposal() because the proposal path validates header shape, successor relation, proposer, body root, and state, but never checks the interlink binding for election blocks. The same finalized block is later rejected by verify_block() during push with InvalidInterlink. Because validators prevote and precommit the malformed header hash itself, the failure happens after Tendermint decides the block, not before voting. This issue has been patched in version 1.3.0.
References
- github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5 (opens in a new tab)
- github.com/nimiq/core-rs-albatross/pull/3668 (opens in a new tab)
- github.com/nimiq/core-rs-albatross/commit/9d7d17c9163384e79f61cdbbfe9853ae57bb8bf7 (opens in a new tab)
- github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0 (opens in a new tab)