CVE-2026-32605: CWE-125: Out-of-bounds Read in nimiq core-rs-albatross
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, an untrusted peer could crash a validator by publishing a signed tendermint proposal message where signer == validators.num_validators(). ProposalSender::send uses > instead of >= for the signer bounds check, so the equality case passes and reaches validators.get_validator_by_slot_band(signer), which panics with an out-of-bounds index before any signature verification runs. This issue has been fixed in version 1.3.0.
AI Analysis
Technical Summary
The vulnerability in nimiq/core-rs-albatross (a Rust implementation of the Nimiq Proof-of-Stake protocol using the Albatross consensus algorithm) is caused by an off-by-one error in the bounds check of the signer index in ProposalSender::send. Specifically, the code uses a '>' comparison instead of '>=' allowing an index equal to the number of validators to be used, leading to an out-of-bounds read and a panic in validators.get_validator_by_slot_band(signer). This occurs before any signature verification, enabling an untrusted peer to crash a validator node. The issue is resolved in version 1.3.0.
Potential Impact
Successful exploitation results in a denial-of-service condition by crashing validator nodes in the Nimiq network. There is no direct impact on confidentiality or integrity, but availability is affected due to the validator crash. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade to nimiq/core-rs-albatross version 1.3.0 or later where this vulnerability is fixed. Patch status is confirmed by the vendor stating the issue is resolved in version 1.3.0. No other mitigations are indicated.
CVE-2026-32605: CWE-125: Out-of-bounds Read in nimiq core-rs-albatross
Description
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, an untrusted peer could crash a validator by publishing a signed tendermint proposal message where signer == validators.num_validators(). ProposalSender::send uses > instead of >= for the signer bounds check, so the equality case passes and reaches validators.get_validator_by_slot_band(signer), which panics with an out-of-bounds index before any signature verification runs. This issue has been fixed in version 1.3.0.
CVSS v3.1
Score 7.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in nimiq/core-rs-albatross (a Rust implementation of the Nimiq Proof-of-Stake protocol using the Albatross consensus algorithm) is caused by an off-by-one error in the bounds check of the signer index in ProposalSender::send. Specifically, the code uses a '>' comparison instead of '>=' allowing an index equal to the number of validators to be used, leading to an out-of-bounds read and a panic in validators.get_validator_by_slot_band(signer). This occurs before any signature verification, enabling an untrusted peer to crash a validator node. The issue is resolved in version 1.3.0.
Potential Impact
Successful exploitation results in a denial-of-service condition by crashing validator nodes in the Nimiq network. There is no direct impact on confidentiality or integrity, but availability is affected due to the validator crash. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade to nimiq/core-rs-albatross version 1.3.0 or later where this vulnerability is fixed. Patch status is confirmed by the vendor stating the issue is resolved in version 1.3.0. No other mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-12T14:54:24.270Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69dd44ab82d89c981f46e0f8
Added to database: 4/13/2026, 7:31:55 PM
Last enriched: 4/21/2026, 5:58:15 AM
Last updated: 6/3/2026, 12:13:59 PM
Views: 90
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.