# CVE-2026-34065: nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals

Source: https://junglewise.ai/threats/cve-2026-34065-nimiq-primitives-node-crash-due-to-missing-interlink-validation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-22. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-34065 · Severity: high · CVSS 7.5 · Published 2026-04-22

nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq's Rust implementation. Prior to version 1.3.0, an untrusted p2p peer can cause a node to panic by announcing an election macro block whose `validators` set contains an invalid compressed BLS voting key. Hashing an election macro header hashes `validators` and reaches `Validators::voting_keys()`, which calls `validator.voting_key.uncompress().unwrap()` and panics on invalid bytes. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.

Technologies: [nimiq-primitives (crates.io)](https://junglewise.ai/threats/technologies/nimiq-primitives), [Nimiq Proof-Of-Stake](https://junglewise.ai/threats/technologies/nimiq-proof-of-stake). Vendors: [crates.io](https://junglewise.ai/threats/vendors/crates-io), [Nimiq](https://junglewise.ai/threats/vendors/nimiq).

## Quick answers

**Is CVE-2026-34065 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-34065 being exploited in the wild.

**How severe is CVE-2026-34065?** High severity, with a CVSS score of 7.5, published 22 April 2026.

**Which products and versions are affected?** nimiq-primitives (crates.io) <= 0.2.0, SEMVER:introduced=0,last_affected=0.2.0.

**Is there a fix for CVE-2026-34065?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**Am I affected by CVE-2026-34065?** Check whether you run nimiq-primitives (crates.io) or Nimiq Proof-Of-Stake at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Affected products

- nimiq-primitives (crates.io) <= 0.2.0, SEMVER:introduced=0,last_affected=0.2.0
- Nimiq Proof-Of-Stake

## Identifiers

- CVE-2026-34065
- GHSA-7c4j-2m43-2mgh

## References

- [https://api.github.com/users/1seal](https://api.github.com/users/1seal)
- [https://github.com/1seal](https://github.com/1seal)
- [https://api.github.com/users/1seal/gists%7B/gist_id%7D](https://api.github.com/users/1seal/gists%7B/gist_id%7D)
- [https://api.github.com/users/1seal/repos](https://api.github.com/users/1seal/repos)
- [https://avatars.githubusercontent.com/u/239602944?v=4](https://avatars.githubusercontent.com/u/239602944?v=4)
- [https://api.github.com/users/1seal/events%7B/privacy%7D](https://api.github.com/users/1seal/events%7B/privacy%7D)

## Related threats

- [Nimiq nimiq-primitives out-of-bounds panic in KeyNibbles::Add](https://junglewise.ai/threats/cve-2026-54542-nimiq-nimiq-primitives-out-of-bounds-panic-in-keynibbles-add)
- [Nimiq nimiq-primitives panic in TrieProof::verify](https://junglewise.ai/threats/cve-2026-54541-nimiq-nimiq-primitives-panic-in-trieproof-verify)
- [Nimiq Albatross denial of service in MerkleRadixTrie synchronization](https://junglewise.ai/threats/cve-2026-46545-nimiq-albatross-denial-of-service-in-merkleradixtrie)
- [Nimiq BlockInclusionProof cryptographic bypass in nimiq-primitives](https://junglewise.ai/threats/cve-2026-46539-nimiq-blockinclusionproof-cryptographic-bypass-in-nimiq)
- [nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge](https://junglewise.ai/threats/cve-2026-34068-nimiq-transaction-updatevalidator-transactions-allows-voting-key)