How to Fix CVE-2026-21666: Remote Code Execution in Backup and Replication

By the Sai Kiran Pandrala · Reviewed and edited by Sai Kiran Pandrala, Editor

What is CVE-2026-21666?

A vulnerability allowing an authenticated domain user to perform remote code execution (RCE) on the Backup Server.

In practical terms, a successful attacker gets remote code execution on the affected system. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Spot the symptom

You're affected if you run Veeam Backup and Replication at any version in the Affected row above. Use these probes to find your installed build:

# Confirm the installed version via your package manager
dpkg -l | grep -i backup   # Debian/Ubuntu
rpm -qa | grep -i backup   # RHEL/CentOS/Rocky

How to fix CVE-2026-21666

The primary fix is to upgrade to the patched build listed in the Fixed in row above (12.3.2). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)

sudo apt-get update
sudo apt-get install --only-upgrade backup-and-replication
# Confirm the installed version meets or exceeds 12.3.2
dpkg -s backup-and-replication | grep ^Version

Linux (RHEL / CentOS / Rocky)

sudo dnf upgrade --security backup-and-replication -y
rpm -q backup-and-replication

Windows (PowerShell, admin)

# Try winget first
winget upgrade --id 'Veeam.Backup and Replication' --silent --accept-source-agreements --accept-package-agreements
# If winget does not know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\BackupandReplication-12.3.2.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows) - detect, back up, upgrade, verify, log

# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\BackupandReplication-Patch-CVE-2026-21666.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-21666 remediation for Veeam Backup and Replication"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Backup*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'12.3.2') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\BackupandReplication-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
# Adjust the source path to match your install
$src = "$env:ProgramFiles\Veeam\Backup and Replication"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer (place the verified file on a share or staging path)
$installer = "$env:TEMP\BackupandReplication-12.3.2.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Backup*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'12.3.2') {
    Write-Log "SUCCESS: now at $verify (>= 12.3.2)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux) - detect, back up, upgrade, verify, log

#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/backup-and-replication-patch-cve-2026-21666.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-21666 remediation for Veeam Backup and Replication"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s backup-and-replication >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' backup-and-replication)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q backup-and-replication >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' backup-and-replication)
    PKG_MGR=dnf
else
    log "backup-and-replication not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: backup-and-replication=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/backup-and-replication-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/backup-and-replication /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y backup-and-replication
else
    sudo dnf upgrade --security -y backup-and-replication
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' backup-and-replication)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' backup-and-replication)
fi
log "After upgrade: $NEW"

# Optionally compare against 12.3.2 with dpkg --compare-versions or sort -V
log "Done. Restart the affected service if the package install did not."

If you can't patch immediately

These are runnable hardening commands. They reduce blast radius but they're not a replacement for the vendor patch.

Rate-limit and log the affected endpoint at the reverse proxy

limit_req_zone $binary_remote_addr zone=admin:10m rate=10r/m;
location /<vulnerable-path> {
    limit_req zone=admin burst=5 nodelay;
    access_log /var/log/nginx/admin-access.log combined;
    proxy_pass http://backend;
}

Full fix path

Run the version probe again and confirm the running build matches the Fixed in row above.

# Confirm the running build matches the patched version listed by the vendor
# Example for Linux package installs:
dpkg -l | grep -i "backup"   # Debian/Ubuntu
rpm -qa | grep -i "backup"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed 12.3.2.

Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-21666 has cleared. Sweep your logs for the indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-21666 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-21666?

CVSS rates it 10 (Critical). Use that score to set your patch priority next to the other items in your queue.

Do I have to take Backup and Replication offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-21666 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://www.veeam.com/kb4830
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21666
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

Written by Sai Kiran Pandrala on 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.

Related fixes

Other defects in the same area that deserve attention during this patch cycle:

• How to Fix CVE-2026-2476: MS Teams plugin sensitive config values not properly masked in support packets
• How to Fix CVE-2026-27962: Authlib JWS JWK Header Injection: Signature Verification Bypass
• How to Fix CVE-2026-25110: Denial of Service in OpenHarmony
• How to Fix CVE-2026-3813: opencc JFlow WF_CCForm.java Calculate injection in JFlow
• How to Fix CVE-2026-30231: Authorization bypass through user-controlled key in Flare