DesktopApplication · Docker
CVE-2026-2664
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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 .
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOut-of-bounds read vulnerability in the grpcfuse kernel module within Docker Desktop's Linux VM. Local attackers can write to /proc/docker entries to trigger the vulnerability, potentially exposing sensitive kernel memory or causing undefined behavior. Fixed in Docker Desktop 4.62.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DesktopApplication
< 4.62.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Docker Desktop versionRun 'docker desktop version' in a terminal or check Docker Desktop UI (Docker icon > Settings > About Docker Desktop)Affected if Version is below 4.62.0
-
Confirm Linux VM is in useDocker Desktop uses a Linux VM for Linux containers. On Windows, check Hyper-V or WSL2 backend status. On Mac, check the virtual machine status.Affected if Linux VM is active and Docker Desktop version is below 4.62.0
-
Verify grpcfuse module presenceWithin the Linux VM, run 'lsmod | grep fuse' or check if /dev/fuse is present. The grpcfuse module is used for mounting Docker volumes.Affected if grpcfuse or fuse kernel module is loaded in the Linux VM with Docker Desktop below 4.62.0
-
Check /proc/docker entriesInspect /proc/docker/ entries in the Linux VM. The CVE states writing to these entries triggers the vulnerability.Affected if User has write access to /proc/docker entries in the Docker Desktop Linux VM and version is below 4.62.0
User is affected if running Docker Desktop version below 4.62.0 with the Linux VM enabled and the grpcfuse module active, allowing access to /proc/docker entries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.62.0
Upgrade Docker Desktop to version 4.62.0 or later. This is the primary remediation as the vulnerability exists in the grpcfuse kernel module which is bundled with Docker Desktop.
Docker Desktop 4.62.0
- 1. Check current Docker Desktop version by clicking the Docker icon and selecting 'About Docker Desktop'
- 2. Download Docker Desktop version 4.62.0 or later from the official Docker website (docker.com/products/docker-desktop)
- 3. Run the installer for your operating system (Windows, Linux, or macOS)
- 4. Follow the on-screen prompts to complete the installation
- 5. Restart Docker Desktop after the upgrade completes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Desktop
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data