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

How to Fix CVE-2026-26136: Microsoft Copilot Information Disclosure in Microsoft Copilot

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

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 6.5, Medium
Actively exploited?No
AffectedMicrosoft Copilot (-)
Fixed inSee vendor advisory
Type (CWE)CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')

What is CVE-2026-26136?

Improper neutralization of special elements used in a command ('command injection') in Microsoft Copilot allows an unauthorized attacker to disclose information over a network.

In practical terms, a successful attacker gets command injection on the host operating 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.

Am I affected?

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


[System.Environment]::OSVersion.Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

How to fix CVE-2026-26136

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.

Linux (Ubuntu / Debian)


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26136
sudo apt-get update
sudo apt-get install --only-upgrade microsoft-copilot
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s microsoft-copilot | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security microsoft-copilot -y
rpm -q microsoft-copilot

Windows (PowerShell, admin)


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26136
# Try winget first
winget upgrade --id 'Microsoft.Microsoft Copilot' --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\MicrosoftCopilot-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait

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


# Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26136
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\MicrosoftCopilot-Patch-CVE-2026-26136.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-26136 remediation for Microsoft Microsoft Copilot"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Microsoft*' } |
    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\MicrosoftCopilot-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\Microsoft\Microsoft Copilot"
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\MicrosoftCopilot-<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 '*Microsoft*' } |
    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://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26136
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/microsoft-copilot-patch-cve-2026-26136.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-26136 remediation for Microsoft Microsoft Copilot"

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

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

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' microsoft-copilot)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' microsoft-copilot)
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.

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;
}

How to verify the fix worked

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


Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected output: the KB ID listed in the vendor advisory appears with an InstalledOn date that matches your patch window.

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

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

Do I have to take Microsoft Copilot 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-26136 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.*