Is CVE-2026-32605 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-32605 being exploited in the wild.

How severe is CVE-2026-32605?

High severity, with a CVSS score of 7.5, published 13 April 2026.

Which products and versions are affected?

Nimiq core-rs-albatross (nimiq-validator) < 1.3.0.

Is there a fix for CVE-2026-32605?

A patch was published on 2026-03-27: Fix merged and version 1.3.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-32605 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-32605?

Check whether you run Nimiq Proof-Of-Stake. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-32605: Nimiq core-rs-albatross denial of service via off-by-one error

Q: Is there a fix for CVE-2026-32605?

A patch was published on 2026-03-27: Fix merged and version 1.3.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-32605 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-32605?

Check whether you run Nimiq Proof-Of-Stake. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-32605 · Severity: high · CVSS 7.5 · Published 2026-04-13

Nimiq Albatross is a blockchain protocol implementation used for processing cryptocurrency transactions. A vulnerability in the validator component allows an unauthenticated attacker to remotely crash the server by sending a specially crafted message. This results in a denial-of-service, potentially disrupting the consensus network and halting transaction processing.

Technologies: Nimiq Proof-Of-Stake. Vendors: Nimiq.

Quick answers

Is CVE-2026-32605 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-32605 being exploited in the wild.
How severe is CVE-2026-32605?: High severity, with a CVSS score of 7.5, published 13 April 2026.
Which products and versions are affected?: Nimiq core-rs-albatross (nimiq-validator) < 1.3.0.
Is there a fix for CVE-2026-32605?: A patch was published on 2026-03-27: Fix merged and version 1.3.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-32605 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-32605?: Check whether you run Nimiq Proof-Of-Stake. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An off-by-one error exists in the `ProposalSender::send` function within the `nimiq-validator` crate. The code uses a `>` operator instead of `>=` when performing a bounds check on the `signer` field of a Tendermint proposal message against the total number of validators. If an untrusted peer sends a message where the signer index is exactly equal to the number of validators, the check passes and triggers a call to `validators.get_validator_by_slot_band(signer)`. This results in an out-of-bounds index panic, crashing the process before signature verification occurs. The issue is fixed in version 1.3.0.

Affected products

Nimiq core-rs-albatross (nimiq-validator) < 1.3.0

Timeline

2026-03-27: patched: Fix merged and version 1.3.0 released
2026-04-11: advisory: GitHub Security Advisory published
2026-04-13: disclosed: CVE-2026-32605 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.