● Medium · CVSS 6.8

How to Fix CVE-2026-34068: CWE-347: Improper Verification of Cryptographic Signature in nimiq-transaction

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

As of 2026-05-25, CVE-2026-34068 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-34068?

The CVSS base score is 6.8 (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-5210: Arbitrary File Read in Leave Application System — Arbitrary File Read in Leave Application System
How to Fix CVE-2026-0608: Critical Vulnerability in Head Meta Data — Critical Vulnerability in Head Meta Data
How to Fix CVE-2026-33220: Path traversal in weblate , Path traversal in weblate
How to Fix CVE-2026-20968: Use-After-Free in Samsung Mobile Devices , Use-After-Free in Samsung Mobile Devices
How to Fix CVE-2026-44586: Cross-Site Scripting in siyuan , Cross-Site Scripting in siyuan

Last verified: 2026-05-25

CVE-2026-34068 is a cwe-347: improper verification of cryptographic signature in nimiq nimiq-transaction. Fix it by upgrading to the patched build from the vendor advisory.

⚡ At a glance


Severity	CVSS 6.8 - Medium
Actively exploited?	Not currently in the CISA KEV catalog
Affected	nimiq-transaction < 1.3.0
Fixed in	See vendor advisory
Type (CWE)	CWE-347: CWE-347: Improper Verification of Cryptographic Signature

What is CVE-2026-34068?

CVE-2026-34068 is a cwe-347: improper verification of cryptographic signature flaw in nimiq nimiq-transaction. It carries a CVSS base score of 6.8 (medium). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: nimiq-transaction provides the transaction primitive to be used in Nimiq's Rust implementation. Prior to version 1.3.0, the staking contract accepts UpdateValidator transactions that set new_voting_key=Some(...) while omitting new_proof_of_knowledge. this skips the proof-of-knowledge requirement that is needed to prevent BLS rogue-key attacks when public keys are aggregated. Because tendermint macro block justification verification aggregates validator voting keys and verifies a single aggregated BLS signature against that aggregate public key, a rogue-key voting key in the validator set can allow an attacker to forge a quorum-looking justification while only producing a single signature.

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-transaction 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-34068

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-transaction.

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-pf4j-pf3w-95f9
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-34068 being exploited in the wild?