CVE-2026-34069 nimiq CVE debrief

Who should care

Defenders responsible for Nimiq Proof-of-Stake protocol deployments, operators of affected platforms, and security teams should assess their exposure to this vulnerability and prioritize upgrading to version 1.3.0 or later. They should also review compensating controls for exposed systems and verify relevant monitoring, detection, and logs for exposed assets.

Why it matters

Defenders should prioritize verifying their exposure to this vulnerability and upgrading to version 1.3.0 or later to prevent potential denial of service.

• Potential denial of service due to panic in the RequestMacroChain message handler task
• Need to verify exposure to this vulnerability and upgrade to version 1.3.0 or later

Technical summary

The RequestMacroChain message handler task in the Nimiq Proof-of-Stake protocol implementation is vulnerable to a panic caused by an unauthenticated p2p peer. The issue arises when the first locator hash on the victim's main chain is a micro block hash, not a macro block hash. The panic occurs because the RequestMacroChain::handle handler selects the locator based only on 'is on main chain' and then calls get_macro_blocks(), which panics via .unwrap() when the selected hash is not a macro block. Defenders should prioritize verifying their exposure to this vulnerability and upgrading to version 1.3.0 or later.

Defensive priority

Defenders should prioritize verifying their exposure to this vulnerability and upgrading to version 1.3.0 or later.

Recommended defensive actions

• Verify exposure to this vulnerability
• Review the official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Upgrade to version 1.3.0 or later

Evidence notes

The vulnerability is caused by the RequestMacroChain::handle handler selecting a locator based only on 'is on main chain' and then calling get_macro_blocks(), which panics via .unwrap() when the selected hash is not a macro block. The issue arises when the first locator hash on the victim's main chain is a micro block hash, not a macro block hash. Defenders should verify their exposure to this vulnerability and review the official advisory or CVE record for affected scope, severity, and vendor guidance.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.