How to Fix CVE-2026-40880: Cwe-1025: comparison using wrong factors in zebra-consensus
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 7.2 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | ZcashFoundation zebrad < 4.3.1; ZcashFoundation zebra-consensus < 5.0.2 |
| Fixed in | zebrad 4.3.1; zebra-consensus 5.0.2 |
| Type (CWE) | CWE-1025: CWE-1025: Comparison Using Wrong Factors |
What is CVE-2026-40880?
ZEBRA is a Zcash node written entirely in Rust. Prior to zebrad version 4.3.1 and zebra-consensus version 5.0.2, a logic error in Zebra's transaction verification cache could allow a malicious miner to induce a consensus split. By carefully submitting a transaction that is valid for height H+1 but invalid for H+2 and then mining that transaction in a block at height H+2, a miner could cause vulnerable Zebra nodes to accept an invalid block, leading to a consensus split from the rest of the Zcash network. This vulnerability is fixed in zebrad version 4.3.1 and zebra-consensus version 5.0.2.
Am I affected?
Run the version check that matches your platform:
# Linux
dpkg -s zebra 2>/dev/null | grep -i version
rpm -q zebra 2>/dev/null
zebra --version 2>/dev/null
Compare what you see against the Affected row above (ZcashFoundation zebrad < 4.3.1; ZcashFoundation zebra-consensus < 5.0.2). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-40880
The primary fix is to upgrade zebra-consensus to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: zebrad 4.3.1; zebra-consensus 5.0.2.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade zebra
zebra --version 2>/dev/null || dpkg -s zebra | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --security zebra -y
rpm -q zebra
SUSE / openSUSE
sudo zypper patch --category security
rpm -q zebra
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-40880 affecting zebra-consensus
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-40880-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detecting installed version of zebra-consensus"
$pkg = winget list --id "zebra_consensus" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\zebra_consensus-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\zebra_consensus" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to zebrad 4.3.1; zebra-consensus 5.0.2"
winget upgrade --id "zebra_consensus" --silent --accept-source-agreements --accept-package-agreements
# Fallback: Windows Update for OS-level fixes
if ($LASTEXITCODE -ne 0) {
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verifying patched build"
winget list --id "zebra_consensus"
Write-Host "Fix applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-40880 affecting zebra-consensus
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-40880-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
dpkg -s zebra 2>/dev/null | grep -i version || echo "zebra not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q zebra || echo "zebra not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-40880-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/zebra /etc/zebra.d /etc/zebra.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Applying upgrade (target: zebrad 4.3.1; zebra-consensus 5.0.2)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y zebra
elif command -v dnf >/dev/null; then
dnf upgrade --security -y zebra
elif command -v yum >/dev/null; then
yum update -y zebra
elif command -v zypper >/dev/null; then
zypper --non-interactive patch --category security
fi
echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
dpkg -s zebra 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q zebra
fi
echo "Done. Restart any running daemons that loaded the old library."
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Network restriction (Linux, nftables)
# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop zebra
sudo systemctl disable zebra
How to verify the fix worked
# Linux
zebra --version 2>/dev/null || dpkg -s zebra | grep -i version
rpm -q zebra 2>/dev/null || true
# Windows
winget list | findstr /I "zebra"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above zebrad 4.3.1; zebra-consensus 5.0.2. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-33442: SQL Injection in kysely — SQL Injection in kysely
- How to Fix CVE-2026-34950: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in fast-jwt — CWE-327: Use of a Broken or Risky Cryptographic Algorithm in fast-jwt
- How to Fix CVE-2026-23971: Deserialization RCE in WoodMart , Deserialization RCE in WoodMart
- How to Fix CVE-2026-2188: Command Injection in 进取 521G , Command Injection in 进取 521G
- How to Fix CVE-2026-5964: SQL injection in EasyFlow .NET , SQL injection in EasyFlow .NET
Is CVE-2026-40880 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
7.2 (high). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-xvj8-ph7x-65gf
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40880
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*