Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

nimiq-block

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.6crates.ioAmendedPublished

    nimiq-block has skip block quorum bypass via out-of-range BitSet indices & u16 truncation

    CVE-2026-33471 · GHSA-6973-8887-87ff

    Affected
    • crates.io nimiq-block < 1.7.2
    Fixed in
    1.7.2· Vendor fix available
    Issue
    Impact `SkipBlockProof::verify` computes its quorum check using `BitSet.len()`, then iterates `BitSet` indices and casts each `usize` index to `u16` (`slot as u16`) for slot lookup. If an attacker can get a `SkipBlockProof` verified where `MultiSignature.signers` contains out-of-range indices spaced by 65536, these indices inflate `len()` but collide onto the same in-range `u16` slot during aggregation. This makes it possible for a malicious validator with far fewer than `2f+1` real signer slots to pass skip block proof verification by multiplying a single BLS signature by the same factor. Patches The patch for this vulnerability is included as part of v1.3.0. Workarounds No known workarounds.

    Recommended action: Upgrade to 1.7.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.com (1)osv.dev (2)Source checked Evidence →