PT-2026-34547 · Unknown · Nimiq-Blockchain

Published 2026-04-22 · Updated 2026-04-23 · CVE-2026-34066

Positive Technologies (AI Summary)

CVSS v3.1

5.3

Medium

Base vector

AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H

Name of the Vulnerable Software and Affected Versions nimiq-blockchain versions prior to 1.3.0

Description In the Rust implementation of Nimiq, the HistoryStore::put historic txns function uses an assert! macro to enforce invariants regarding the block number of a HistoricTransaction, requiring it to be within the same epoch and the macro block being pushed. During a history sync, a peer can provide a malformed history list via the history: &[HistoricTransaction] input passed into Blockchain::push history sync, which can violate these invariants and trigger a panic. This occurs because extend history sync calls this.history store.add to history(..) before the computed history root is compared against the macro block header (block.history root()), allowing the panic to happen before rejection checks are executed.

Recommendations Update to version 1.3.0.

Fix

RCE

Improper Check for Exceptional Conditions

Assertion Failure

Weakness Enumeration

CWE-20

CWE-754

CWE-617

Related Identifiers

CVE-2026-34066

GHSA-J99G-7RQW-Q9JG

Affected Products

Nimiq-Blockchain

References · 8

• https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50 · Patch
• https://github.com/nimiq/core-rs-albatross/pull/3656 · Patch
• https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg · Vendor Advisory
• https://osv.dev/vulnerability/GHSA-j99g-7rqw-q9jg · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2026-34066 · Security Note
• https://github.com/nimiq/core-rs-albatross · Note
• https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0 · Note
• https://twitter.com/CVEnew/status/2047359955846463569 · Twitter Post