● Medium · CVSS 5.3

How to Fix CVE-2026-34064: CWE-191: Integer Underflow (Wrap or Wraparound) in nimiq-account

Q: Is CVE-2026-34064 being exploited in the wild?

As of 2026-05-25, CVE-2026-34064 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

Q: What is the CVSS score for CVE-2026-34064?

The CVSS base score is 5.3 (Medium).

Q: What version fixes this?

The vendor advisory names the patched build. See the References section.

Q: Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

By Sai Kiran Pandrala

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-34877: n/a (Bundle Sibling) — n/a (Bundle Sibling)
How to Fix CVE-2026-40618: Critical Vulnerability in BIG-IP — Critical Vulnerability in BIG-IP
How to Fix CVE-2026-25206: Out-of-bounds read in Escargot , Out-of-bounds read in Escargot
How to Fix CVE-2026-4987: Input Validation Flaw in SureForms – Contact Form, Payment Form & Other Custom Form Builder , Input Validation Flaw in SureForms – Contact Form, Payment Form & Other Custom Form Builder
How to Fix CVE-2026-24899: Authentication Bypass in fleet , Authentication Bypass in fleet

Last verified: 2026-05-25

CVE-2026-34064 is a cwe-191: integer underflow (wrap or wraparound) in nimiq nimiq-account. Fix it by upgrading to the patched build from the vendor advisory.

⚡ At a glance


Severity	CVSS 5.3 - Medium
Actively exploited?	Not currently in the CISA KEV catalog
Affected	nimiq-account < 1.3.0
Fixed in	See vendor advisory
Type (CWE)	CWE-191: CWE-191: Integer Underflow (Wrap or Wraparound)

What is CVE-2026-34064?

CVE-2026-34064 is a cwe-191: integer underflow (wrap or wraparound) flaw in nimiq nimiq-account. It carries a CVSS base score of 5.3 (medium). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: 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.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of nimiq-account matches a version listed in the Affected row above.

Check the running version against the Affected row above using the product's admin console or --version flag.

How to fix CVE-2026-34064

Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for nimiq-account.

Generic upgrade pattern

If the affected product is a Linux package, upgrade via the system package manager:


# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y

# RHEL / Rocky / Alma
sudo dnf upgrade --security -y

If it ships as a Windows installer, download the patched build from the vendor advisory and:


# Vendor advisory: https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
    Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion

After applying the patch

Restart the service or device so the patched binary loads.
Confirm the running version matches the Fixed in row using the verification command below.
Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.


# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

Check the running version against the Affected row above using the product's admin console or --version flag.

Expected: a version at or above the patched build named in the vendor advisory.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

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