What is CVE-2026-34064?

nimiq-account contains account primitives to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance balance`, the node crashes while trying to return an error. The `min_cap > balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validati

How severe is CVE-2026-34064?

CVE-2026-34064 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which products are affected by CVE-2026-34064?

Affected package information for CVE-2026-34064 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2026-34064?

Apply the nimiq nimiq proof-of-stake security patch or hotfix for CVE-2026-34064 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2026-34064 across my infrastructure?

Inventory every nimiq nimiq proof-of-stake deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2026-34064 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2026-34064?

O3 detects and blocks CVE-2026-34064 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2026-34064 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-34064 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-34064?

CVE-2026-34064 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-34064?

CVE-2026-34064 is classified as CWE-191 (CWE-191). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2026-34064?

CVE-2026-34064 affects nimiq nimiq proof-of-stake. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-34064 published, and has it been updated?

CVE-2026-34064 was published on April 22, 2026 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2026-34064

MEDIUM

nimiq-account contains account primitives to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds`…

Published

Apr 22, 2026

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk19th percentile+0.24%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

nimiq-account contains account primitives to be used in Nimiq's Rust implementation. Prior to version 1.3.0, VestingContract::can_change_balance returns AccountError::InsufficientFunds when new_balance < min_cap, but it constructs the error using balance: self.balance - min_cap. Coin::sub panics on underflow, so if an attacker can reach a state where min_cap > balance, the node crashes while trying to return an error. The min_cap > balance precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding total_amount without validating total_amount <= transaction.value (the real contract balance). After creating such a vesting contract, the attacker can broadcast an outgoing transaction to trigger the panic during mempool admission and block processing. The patch for this vulnerability is included as part of v1.3.0. No known workarounds are available.

Affected Products

1 product · 1 configurations

Application

nimiq proof-of-stakenimiq

< 1.3.0

range

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every nimiq nimiq proof-of-stake deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the nimiq nimiq proof-of-stake security patch or hotfix for CVE-2026-34064 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2026-34064 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2026-34064. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

nimiq-account contains account primitives to be used in Nimiq's Rust implementation. Prior to version 1.3.0, `VestingContract::can_change_balance` returns `AccountError::InsufficientFunds` when `new_balance < min_cap`, but it constructs the error using `balance: self.balance - min_cap`. `Coin::sub` panics on underflow, so if an attacker can reach a state where `min_cap > balance`, the node crashes while trying to return an error. The `min_cap > balance` precondition is attacker-reachable because the vesting contract creation data (32-byte format) allows encoding `total_amount` without validati

O3 Security · Runtime Protection

Is CVE-2026-34064 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2026-34064 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works