CVE-2026-34066 json
nimiq-blockchain: Peer-triggerable panic during history sync
published 2026-04-22 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-25064 , GHSA-j99g-7rqw-q9jg
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryStore::put_historic_txns` uses an `assert!` to enforce invariants about `HistoricTransaction.block_number` (must be within the macro block being pushed and within the same epoch). During history sync, a peer can influence the `history: &[HistoricTransaction]` input passed into `Blockchain::push_history_sync`, and a malformed history list can violate these invariants and trigger a panic. `extend_history_sync` calls `this.history_store.add_to_history(..)` before comparing the computed history root against the macro block header (`block.history_root()`), so the panic can happen before later rejection checks run. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
Patch / fix
- nimiq nimiq-blockchain 1.3.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | nimiq-blockchain | <=0.2.0 |
no fix listed |
Affected products
- nimiq nimiq-blockchain
Classification
References
-
github.com
/nimiq/core-rs-albatross/pull/3656
web, issue-tracking, patch
-
github.com
/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50
web, patch
-
github.com
/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg
web, patch, vendor-advisory
-
github.com
/nimiq/core-rs-albatross/releases/tag/v1.3.0
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-34066
advisory
-
github.com
/nimiq/core-rs-albatross
package
Sources
- CVE List CVE-2026-34066
- GitHub Advisory GHSA-j99g-7rqw-q9jg
- NVD CVE-2026-34066
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.