# CVE-2026-34064: nimiq-account: Vesting insufficient funds error can panic

> An attacker can crash a Nimiq node by triggering an integer underflow panic in the vesting contract logic via crafted transaction data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 23 Apr 2026
- **Also known as:** GHSA-vc34-39q2-m6q3

## What is CVE-2026-34064?

CVE-2026-34064 is a medium-severity vulnerability in nimiq-account, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2026-34064?

2 open source packages ship an affected version, including nimiq-account. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nimiq-account` | crates.io | All versions to 0.2.0 | None |
| `nimiq-account` | crates.io | All versions to 0.2.0 | None |

Products: Nimiq Nimiq Proof-of-Stake.

## How do I fix CVE-2026-34064?

No fix has been published for CVE-2026-34064 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34064 being exploited?

There is no known exploitation of CVE-2026-34064 in the wild and no public exploit code.

## Other vulnerabilities in nimiq-account

- [CVE-2026-33471](https://insights.sbomify.com/CVE-2026-33471/): nimiq-block has skip block quorum bypass via out-of-range BitSet indices & u16 truncation (critical 9.6)
- [CVE-2026-40093](https://insights.sbomify.com/CVE-2026-40093/): nimiq-blockchain is missing a wall-clock upper bound on block timestamps (high 8.1)
- [CVE-2026-34063](https://insights.sbomify.com/CVE-2026-34063/): network-libp2p: Peer can crash the node by opening discovery protocol substream twice (high 7.5)
- [CVE-2026-34065](https://insights.sbomify.com/CVE-2026-34065/): nimiq-primitives: Node crash due to missing interlink validation in election macro block proposals (high 7.5)
- [CVE-2026-32605](https://insights.sbomify.com/CVE-2026-32605/): Nimiq: Remote crash via off-by-one signer bounds check in proposal buffer (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34064 and fix it if it is affected.

What it is: CVE-2026-34064 is a medium-severity vulnerability in nimiq-account, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34064 in the wild and no public exploit code.

Affected packages and fixed versions:
- nimiq-account (crates.io): affected all versions up to 0.2.0; no fix listed
- nimiq-account (crates.io): affected all versions up to 0.2.0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34064/ (Markdown: https://insights.sbomify.com/CVE-2026-34064/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34064
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34064
- OSV: https://osv.dev/vulnerability/CVE-2026-34064

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34064/
Summaries are generated and may contain mistakes; the official description above is the record.