How severe is CVE-2026-34067?

CVE-2026-34067 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability low.

Is CVE-2026-34067 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-34067?

CVE-2026-34067 affects Nimiq Nimiq Proof-of-stake. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-34067?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-34067 have an EU (EUVD) identifier?

Yes. CVE-2026-34067 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25084.

When was CVE-2026-34067 published?

CVE-2026-34067 was published on 2026-04-22 and last updated on 2026-06-17.

CVE-2026-34067

CVE-2026-34067 is a low-severity vulnerability in Nimiq Nimiq Proof-of-stake with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-617.

Key facts

Severity: Low (CVSS 3.x base score 3.1)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-25084
Weakness: CWE-617
Affected product: Nimiq Nimiq Proof-of-stake
Published: 2026-04-22
Last modified: 2026-06-17

Description

nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.

Frequently asked questions

What is CVE-2026-34067?: nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `HistoryTreeProof::verify` panics on a malformed proof where `history.len() != positions.len()` due to `assert_eq!(history.len(), positions.len())`. The proof object is derived from untrusted p2p responses (`ResponseTransactionsProof.proof`) and is therefore attacker-controlled at the network boundary until validated. A malicious peer could trigger a crash by returning a crafted inclusion proof with a length mismatch. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.
How severe is CVE-2026-34067?: CVE-2026-34067 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2026-34067 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-34067?: CVE-2026-34067 affects Nimiq Nimiq Proof-of-stake. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-34067?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-34067 have an EU (EUVD) identifier?: Yes. CVE-2026-34067 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25084.
When was CVE-2026-34067 published?: CVE-2026-34067 was published on 2026-04-22 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:nimiq:nimiq_proof-of-stake:*:*:*:*:*:rust:*:*

More vulnerabilities in Nimiq Nimiq Proof-of-stake

CVE-2026-33471 — Critical (CVSS 9.6): nimiq-block contains block primitives to be used in Nimiq's Rust implementation. `SkipBlockProof::verify` computes its…
CVE-2026-40093 — High (CVSS 8.1): nimiq-blockchain provides persistent block storage for Nimiq's Rust implementation. In 1.3.0 and earlier, block…
CVE-2026-34065 — High (CVSS 7.5): nimiq-primitives contains primitives (e.g., block, account, transaction) to be used in Nimiq's Rust implementation.…
CVE-2026-34063 — High (CVSS 7.5): Nimiq's network-libp2p is a Nimiq network implementation based on libp2p. Prior to version 1.3.0, `network-libp2p`…
CVE-2026-32605 — High (CVSS 7.5): nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus…
CVE-2026-33184 — High (CVSS 7.5): nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus…

All CVEs affecting Nimiq Nimiq Proof-of-stake →

Other CWE-617 (Reachable Assertion) vulnerabilities

CVE-2020-3615 — Critical (CVSS 9.8): Valid deauth/disassoc frames is dropped in case if RMF is enabled and some rouge peer keep on sending rogue…
CVE-2019-9795 — Critical (CVSS 9.8): A vulnerability where type-confusion in the IonMonkey just-in-time (JIT) compiler could potentially be used by…
CVE-2026-31739 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The…
CVE-2020-12417 — High (CVSS 8.8): Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in…
CVE-2020-6623 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_get_index.
CVE-2020-6619 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__buf_seek.

Browse all CWE-617 (Reachable Assertion) vulnerabilities →