● Low · CVSS 2

How to Fix CVE-2026-3194: Missing authentication in Blockchain

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

2 (Low). Vector: `CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`.

Q: Where is the official advisory for CVE-2026-3194?

The vendor advisory is at [https://vuldb.com/?id.347750](https://vuldb.com/?id.347750). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3194.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-3194 is a missing authentication in Chia Blockchain. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	2 (Low)
Actively exploited?	No public listing in CISA KEV
Affected	Blockchain 2.1.0
Fixed in	See vendor advisory
Type (CWE)	CWE-306: Missing Authentication

What is CVE-2026-3194?

A flaw has been found in Chia Blockchain 2.1.0. The affected element is the function send_transaction/get_private_key of the component RPC Server Master Passphrase Handler. This manipulation causes missing authentication. The attack can only be executed locally. The attack's complexity is rated as high. The exploitability is described as difficult. The exploit has been published and may be used. The vendor was informed early via email. A separate report via bugbounty was rejected with the reason "This is by design. The user is responsible for host security". The CVSS base score is 2 (Low). The official advisory is at https://vuldb.com/?id.347750.

Am I affected?

Check the version of Blockchain you are running and compare it against the Affected row above (Blockchain 2.1.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s blockchain 2>/dev/null | grep -i ^Version
rpm -q blockchain 2>/dev/null
command -v blockchain >/dev/null && blockchain --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Blockchain*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Blockchain" 2>$null

How to fix CVE-2026-3194

Upgrade Blockchain to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade blockchain
dpkg -s blockchain | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh blockchain -y
# or for older releases:
sudo yum update blockchain -y
rpm -q blockchain

SUSE / openSUSE


sudo zypper refresh
sudo zypper update blockchain
rpm -q blockchain

Node.js / npm


# Update the affected package in your project
npm install Blockchain@latest
npm ls Blockchain
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-3194 affecting Blockchain
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-3194-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] Detect installed version"
    $pkg = Get-Package -Name "*Blockchain*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\blockchain-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Blockchain" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Blockchain" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Blockchain"
    Write-Host "Patch 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-3194 affecting Blockchain
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-3194-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s blockchain 2>/dev/null | grep -i ^Version || echo "blockchain not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q blockchain || echo "blockchain not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-3194-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/blockchain /etc/blockchain.d /etc/blockchain.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y blockchain
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y blockchain
elif command -v yum >/dev/null; then
    yum update -y blockchain
elif command -v zypper >/dev/null; then
    zypper --non-interactive update blockchain
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s blockchain 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q blockchain
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-3194" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-3194"

Disable the affected service (Linux)


sudo systemctl stop blockchain 2>/dev/null || true
sudo systemctl disable blockchain 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s blockchain 2>/dev/null | grep -i ^Version
rpm -q blockchain 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Blockchain*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

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

How to Fix CVE-2026-0787: Command Injection in 8180 IP Audio Alerter — Command Injection in 8180 IP Audio Alerter
How to Fix CVE-2026-34558: Critical Vulnerability in ci4ms — Critical Vulnerability in ci4ms
How to Fix CVE-2026-39425: Cwe-80: improper neutralization of script-related html in MaxKB , Cwe-80: improper neutralization of script-related html in MaxKB
How to Fix CVE-2026-44459: Access Control Bypass in hono , Access Control Bypass in hono
How to Fix CVE-2026-48232: SQL Injection in Tickets , SQL Injection in Tickets

Is CVE-2026-3194 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-3194?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-3194?

2 (Low). Vector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P.

Where is the official advisory for CVE-2026-3194?

The vendor advisory is at https://vuldb.com/?id.347750. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3194.

References

Official vendor advisory: https://vuldb.com/?id.347750
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3194
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://vuldb.com/?ctiid.347750
Additional reference: https://vuldb.com/?submit.757201
Additional reference: https://github.com/Danimlzg/chia-rpc-auth-bypass.git

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