● Medium · CVSS 6.8

How to Fix CVE-2026-2664: Out-of-bounds read in Docker Desktop

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

6.8 (Medium). Vector: `CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`.

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

The vendor advisory is at [https://docs.docker.com/desktop/release-notes/#4620](https://docs.docker.com/desktop/release-notes/#4620). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2664.

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

CVE-2026-2664 is a out-of-bounds read in Docker Docker Desktop. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	6.8 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	Docker Desktop 0 to <4.62.0
Fixed in	See vendor advisory
Type (CWE)	CWE-125 Out-of-bounds Read

What is CVE-2026-2664?

An out of bounds read vulnerability in the grpcfuse kernel module present in the Linux VM in Docker Desktop for Windows, Linux and macOS up to version 4.61.0 could allow a local attacker to cause an unspecified impact by writing to /proc/docker entries. The issue has been fixed in Docker Desktop 4.62.0 . The CVSS base score is 6.8 (Medium). The official advisory is at https://docs.docker.com/desktop/release-notes/#4620.

Am I affected?

Check the version of Docker Desktop you are running and compare it against the Affected row above (Docker Desktop 0 to <4.62.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 docker-desktop 2>/dev/null | grep -i ^Version
rpm -q docker-desktop 2>/dev/null
command -v docker-desktop >/dev/null && docker-desktop --version 2>/dev/null


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

How to fix CVE-2026-2664

Upgrade Docker Desktop 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 docker-desktop
dpkg -s docker-desktop | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update docker-desktop
rpm -q docker-desktop

Node.js / npm


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

Container image


docker pull docker-desktop:latest
# In Kubernetes:
kubectl set image deploy/docker-desktop docker-desktop=docker-desktop:latest

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-2664 affecting Docker Desktop
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-2664-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 "*Docker Desktop*" -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\docker-desktop-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Docker Desktop" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Docker Desktop" --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 "Docker Desktop"
    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-2664 affecting Docker Desktop
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-2664-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 docker-desktop 2>/dev/null | grep -i ^Version || echo "docker-desktop not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q docker-desktop || echo "docker-desktop not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-2664-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/docker-desktop /etc/docker-desktop.d /etc/docker-desktop.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 docker-desktop
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y docker-desktop
elif command -v yum >/dev/null; then
    yum update -y docker-desktop
elif command -v zypper >/dev/null; then
    zypper --non-interactive update docker-desktop
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s docker-desktop 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q docker-desktop
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-2664" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-2664"

Disable the affected service (Linux)


sudo systemctl stop docker-desktop 2>/dev/null || true
sudo systemctl disable docker-desktop 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 docker-desktop 2>/dev/null | grep -i ^Version
rpm -q docker-desktop 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 "*Docker Desktop*" | 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-1839: Deserialization of Untrusted Data in huggingface/transformers — Deserialization of Untrusted Data in huggingface/transformers
How to Fix CVE-2026-28286: External control of file name or path in ZimaOS — External control of file name or path in ZimaOS
How to Fix CVE-2026-3960: CWE-94 Improper Control of Generation of Code in h2oai/h2o-3 , CWE-94 Improper Control of Generation of Code in h2oai/h2o-3
How to Fix CVE-2026-40866: Cwe-284: improper access control in horilla , Cwe-284: improper access control in horilla
How to Fix CVE-2026-25495: SQL Injection in cms , SQL Injection in cms

Is CVE-2026-2664 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-2664?

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-2664?

6.8 (Medium). Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N.

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

The vendor advisory is at https://docs.docker.com/desktop/release-notes/#4620. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2664.

References

Official vendor advisory: https://docs.docker.com/desktop/release-notes/#4620
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2664
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

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