Advisory

GHSA-pf4j-pf3w-95f9

Also known as: CVE-2026-34068

Summary

nimiq-transaction: UpdateValidator transactions allows voting key change without proof-of-knowledge

Details

Impact
The staking contract accepts UpdateValidator transactions that set new_voting_key=Some(...) while omitting new_proof_of_knowledge. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated.

Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature.

While the impact is critical, the exploitability is low: The voting keys are fixed for the epoch, so the attacker would need to know the next epoch validator set (chosen through VRF), which is unlikely.

Patches
The patch for this vulnerability is included as part of v1.3.0.

Workarounds
No known workarounds.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-22 19:22 UTC
Modified
2026-05-05 16:09 UTC

Affected packages and fixes

nimiq-transaction

crates.io · All systems

Affected

  • introduced 0, last affected 0.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences