⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.8

How to Fix CVE-2026-20040: Cisco IOS XR Software CLI Privilege Escalation in Cisco IOS XR Software

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

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.8, High
Actively exploited?No
AffectedCisco IOS XR Software (6.5.3, 6.5.29, 6.5.1)
Fixed inSee vendor advisory
Type (CWE)CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

What is CVE-2026-20040?

A vulnerability in the CLI of Cisco IOS XR Software could allow an authenticated, local attacker to execute arbitrary commands as root on the underlying operating system of an affected device. This vulnerability is due to insufficient validation of user arguments that are passed to specific CLI commands. An attacker with a low-privileged account could exploit this vulnerability by using crafted commands at the prompt.

In practical terms, a successful attacker gets compromise of the affected component as described in the vendor advisory. 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.

Am I affected?

You're affected if you run Cisco IOS XR Software at any version in the Affected row above. Use these probes to find your installed build:


show version | include Version

How to fix CVE-2026-20040

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

Cisco IOS / IOS XE / IOS XR (CLI)


# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxr-privesc-bF8D5U4W
enable
# Confirm running image and version
show version | include Version
# Stage the patched image (use the verified build from the advisory, e.g. <patched-version>)
copy ftp://upload-server/cisco-ios-xr-software-<patched-version>.bin flash:
# Make the new image the boot image
configure terminal
 boot system flash:cisco-ios-xr-software-<patched-version>.bin
 end
write memory
reload

Cisco ASA / FTD (ASDM or CLI upgrade)


# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxr-privesc-bF8D5U4W
enable
show version
copy tftp://10.0.0.10/asa<patched-version>-smp-k8.bin disk0:
configure terminal
 boot system disk0:/asa<patched-version>-smp-k8.bin
 end
write memory
reload

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


# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxr-privesc-bF8D5U4W
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\CiscoIOSXRSoftware-Patch-CVE-2026-20040.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-20040 remediation for Cisco Cisco IOS XR Software"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Cisco*' } |
    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]'<patched-version>') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\CiscoIOSXRSoftware-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\Cisco\Cisco IOS XR Software"
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\CiscoIOSXRSoftware-<patched-version>.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 '*Cisco*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
    Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

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


# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxr-privesc-bF8D5U4W
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/cisco-ios-xr-software-patch-cve-2026-20040.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-20040 remediation for Cisco Cisco IOS XR Software"

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

# 2. Backup config
BACKUP=/var/backups/cisco-ios-xr-software-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/cisco-ios-xr-software /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 cisco-ios-xr-software
else
    sudo dnf upgrade --security -y cisco-ios-xr-software
fi

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

# Optionally compare against <patched-version> 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.

No official vendor workaround is published for this CVE; patching is the only documented fix. The runnable hardening below is generic defense in depth, not a substitute for the patch.

Restrict the affected service to trusted networks (Linux):


# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxr-privesc-bF8D5U4W
# Replace <port> with the affected service port and 10.0.0.0/24 with your admin subnet
sudo iptables -A INPUT -p tcp --dport <port> -s 10.0.0.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport <port> -j DROP

Windows Firewall equivalent:


# Vendor advisory: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-iosxr-privesc-bF8D5U4W
New-NetFirewallRule -DisplayName 'Allow affected service from admin subnet' \
    -Direction Inbound -Action Allow -Protocol TCP -LocalPort <port> -RemoteAddress 10.0.0.0/24
New-NetFirewallRule -DisplayName 'Block affected service from everywhere else' \
    -Direction Inbound -Action Block -Protocol TCP -LocalPort <port>

How to verify the fix worked

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


show version | include Version

Expected output: a line that includes the patched build (for example Version the patched build or higher).

Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-20040 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-20040 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-20040?

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

Do I have to take Cisco IOS XR Software 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-20040 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

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