Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2664: CWE-125 Out-of-bounds Read in Docker Docker Desktop

0
Medium
VulnerabilityCVE-2026-2664cvecve-2026-2664cwe-125
Published: Tue Feb 24 2026 (02/24/2026, 10:09:18 UTC)
Source: CVE Database V5
Vendor/Project: Docker
Product: Docker Desktop

Description

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 .

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/03/2026, 20:41:13 UTC

Technical Analysis

CVE-2026-2664 is a medium-severity vulnerability classified as CWE-125 (Out-of-bounds Read) found in the grpcfuse kernel module embedded within the Linux virtual machine that Docker Desktop uses across Windows, Linux, and macOS platforms. The grpcfuse module facilitates file system operations between the host and the containerized Linux environment. The vulnerability arises from improper bounds checking during read operations, allowing a local attacker with limited privileges to perform out-of-bounds reads. This can lead to unauthorized writes to /proc/docker entries, a critical interface for Docker's internal process management. While the exact impact is unspecified, such unauthorized writes could disrupt Docker's operation or leak sensitive information. The vulnerability does not require user interaction or elevated privileges beyond local access, making it a risk primarily for users who already have some level of system access. Docker addressed this issue in version 4.62.0 of Docker Desktop by correcting the bounds checking in grpcfuse, eliminating the out-of-bounds read condition. No public exploits have been reported, but the presence of this flaw in a widely used container management tool underscores the importance of timely patching.

Potential Impact

The vulnerability could allow local attackers to interfere with Docker Desktop's internal process management by writing to /proc/docker entries, potentially leading to denial of service, data leakage, or unauthorized modification of Docker's runtime state. Organizations relying on Docker Desktop for development, testing, or production container management may experience disruptions or compromise of container isolation boundaries if exploited. Although exploitation requires local access, the widespread use of Docker Desktop in enterprise environments means that insider threats or compromised user accounts could leverage this flaw to escalate impact. The unspecified nature of the impact suggests that the vulnerability could be leveraged in various attack scenarios, including container escape or privilege escalation within the Linux VM. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time. Overall, the vulnerability poses a moderate risk to confidentiality, integrity, and availability of containerized workloads managed via Docker Desktop.

Mitigation Recommendations

1. Upgrade Docker Desktop to version 4.62.0 or later immediately to apply the official fix for CVE-2026-2664. 2. Restrict local access to systems running vulnerable Docker Desktop versions to trusted users only, minimizing the risk of exploitation by untrusted local actors. 3. Monitor /proc/docker and related system interfaces for unusual write activity that could indicate exploitation attempts. 4. Employ host-based intrusion detection systems (HIDS) to detect anomalous kernel module behavior or unauthorized modifications to Docker-related processes. 5. Enforce strict user privilege management and limit the use of Docker Desktop to necessary personnel to reduce the attack surface. 6. Regularly audit Docker Desktop configurations and update policies to ensure compliance with security best practices. 7. Consider isolating development environments using Docker Desktop from sensitive production systems to contain potential impacts. 8. Stay informed about any emerging exploit reports or additional patches related to this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Docker
Date Reserved
2026-02-18T08:31:13.158Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699d7ab4be58cf853bad4716

Added to database: 2/24/2026, 10:17:24 AM

Last enriched: 3/3/2026, 8:41:13 PM

Last updated: 4/11/2026, 12:36:13 AM

Views: 333

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses