Consensus forgery via omitted proof-of-knowledge validation
Published Apr 22, 2026 · Updated Apr 22, 2026
Improper signature verification in Nimiq nimiq-transaction before 1.3.0 allows remote attackers to forge macro block justifications. The staking contract accepts an UpdateValidator voting-key change when new_proof_of_knowledge is absent, so aggregate-key verification can include a rogue BLS key. Exploitation requires predicting the next epoch validator set selected by VRF; a successful forgery can make one signature appear to satisfy quorum.
Summary
What happened
Improper signature verification in Nimiq nimiq-transaction before 1.3.0 allows remote attackers to forge macro block justifications. The staking contract accepts an UpdateValidator voting-key change when new_proof_of_knowledge is absent, so aggregate-key verification can include a rogue BLS key. Exploitation requires predicting the next epoch validator set selected by VRF; a successful forgery can make one signature appear to satisfy quorum.
The record
- CVE
- CVE-2026-34068
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- Nimiq
- Product
- nimiq-transaction
- Classifications
- CWE-347, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo