CVE-2026-34066

// Conceptual PoC: Malformed history data triggering the assert // This demonstrates the vulnerability where a panic occurs due to invalid block_number. #[test] fn test_cve_2026_34066_panic() { // Simulate the vulnerable environment prior to v1.3.0 // In a real scenario, this data comes from a malicious peer during sync. // Assume a valid macro block context exists, e.g., Block 100, Epoch 1. let current_macro_block = 100; let current_epoch = 1; // Construct a malicious HistoricTransaction list. // The invariant is: block_number must be within the macro block and same epoch. // We intentionally violate this by setting a block_number from a different epoch/out of bounds. let malicious_history = vec![ HistoricTransaction { block_number: 99999, // Invalid: Violates invariants // ... other fields ... } ]; // The vulnerable function call. // In versions < 1.3.0, put_historic_txns uses `assert!` internally. // Passing the malicious history here triggers the panic immediately. // This simulates the attack path where the node crashes before verifying the hash root. HistoryStore::put_historic_txns(&malicious_history); }

{"cve": {"id": "CVE-2026-34066", "sourceIdentifier": "[email protected]", "published": "2026-04-22T20:16:41.237", "lastModified": "2026-04-24T17:12:43.110", "vulnStatus": "Analyzed", "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}], "metrics": {"cvssMetricV31": [{"source": "[email protected]", "type": "Secondary", "cvssData": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H", "baseScore": 5.3, "baseSeverity": "MEDIUM", "attackVector": "NETWORK", "attackComplexity": "HIGH", "privilegesRequired": "NONE", "userInteraction": "REQUIRED", "scope": "UNCHANGED", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "availabilityImpact": "HIGH"}, "exploitabilityScore": 1.6, "impactScore": 3.6}]}, "weaknesses": [{"source": "[email protected]", "type": "Primary", "description": [{"lang": "en", "value": "CWE-20"}, {"lang": "en", "value": "CWE-617"}, {"lang": "en", "value": "CWE-754"}]}], "configurations": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*", "versionEndExcluding": "1.3.0", "matchCriteriaId": "CD0CAAD1-7626-4A4A-A6F8-9DC46FE50731"}]}]}], "references": [{"url": "https://github.com/nimiq/core-rs-albatross/commit/6f5511309c199d84b012fe6b9aba7e5582892c50", "source": "[email protected]", "tags": ["Patch"]}, {"url": "https://github.com/nimiq/core-rs-albatross/pull/3656", "source": "[email protected]", "tags": ["Issue Tracking", "Patch"]}, {"url": "https://github.com/nimiq/core-rs-albatross/releases/tag/v1.3.0", "source": "[email protected]", "tags": ["Release Notes"]}, {"url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg", "source": "[email protected]", "tags": ["Patch", "Vendor Advisory"]}]}}