{"answers":{"affected":"2 open source packages ship an affected version, including nimiq-block. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33471 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33471 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33471 is a critical vulnerability in nimiq-block, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33471 and fix it if it is affected.\n\nWhat it is: CVE-2026-33471 is a critical vulnerability in nimiq-block, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33471 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nimiq-block (crates.io): affected all versions up to 0.2.0; no fix listed\n- nimiq-block (crates.io): affected all versions up to 0.2.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33471/ (Markdown: https://insights.sbomify.com/CVE-2026-33471/index.md)","id":"CVE-2026-33471","markdown":"https://insights.sbomify.com/CVE-2026-33471/index.md","name":"CVE-2026-33471","record":{"aliases":["GHSA-6973-8887-87ff"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust blockchain library","requires_auth":"low_privilege","summary":"A malicious validator can bypass skip block proof verification in nimiq-block by exploiting integer truncation to inflate quorum counts with out-of-range indices.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nimiq_proof-of-stake","vendor":"nimiq"}],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"}],"description":"nimiq-block contains block primitives to be used in Nimiq's Rust implementation. `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. Prior to version 1.3.0, 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. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"nimiq-block has skip block quorum bypass via out-of-range BitSet indices \u0026 u16 truncation","id":"CVE-2026-33471","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Cryptomator Hub OAuth token exchange HTTP downgrade via getAuthority() scheme confusion (CVE-2026-32303 bypass)","id":"CVE-2026-33472"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-block","purl":null,"source":"GHSA-6973-8887-87ff"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"nimiq-block","purl":"pkg:cargo/nimiq-block","source":"GHSA-6973-8887-87ff"}],"prev":{"headline":"Missing authorization in frigate","id":"CVE-2026-33470"},"products":["nimiq-block"],"published":"2026-04-22","related":[{"cvss_score":8.1,"headline":"nimiq-blockchain is missing a wall-clock upper bound on block timestamps","id":"CVE-2026-40093","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":7.5,"headline":"network-libp2p: Peer can crash the node by opening discovery protocol substream twice","id":"CVE-2026-34063","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.5,"headline":"nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals","id":"CVE-2026-34065","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.5,"headline":"Nimiq: Remote crash via off-by-one signer bounds check in proposal buffer","id":"CVE-2026-32605","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":7.5,"headline":"nimiq/core-rs-albatross: Discovery handshake limit could underflow and later provoke a deterministic overflow panic","id":"CVE-2026-33184","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":7.1,"headline":"nimiq/core-rs-albatross's nimiq-blockchain missing proposal body root verification","id":"CVE-2026-28402","kev_date_added":null,"published":"2026-02-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["nimiq"]},"summary":"A malicious validator can bypass skip block proof verification in nimiq-block by exploiting integer truncation to inflate quorum counts with out-of-range indices.","url":"https://insights.sbomify.com/CVE-2026-33471/"}