Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local low-priv access to Windows host
-
DeliveryStage crafted unsigned package
-
ExploitInvoke Installer.exe install -package
-
ExecutionTrick user into approving Docker UAC prompt
-
ImpactExecute installer actions as LocalSystem
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires the affected product Docker Desktop for Windows at a version before 4.92.0, and specifically the use of the command-line installer feature 'Docker Desktop Installer.exe install -package' with an attacker-supplied package. The attacker must (1) already be able to place or deliver a crafted package on the target host (local access per AV:L), and (2) convince a user to actively approve the Docker-signed UAC elevation prompt (UI:A). The signature of the supplied package is not verified, which is the root flaw. Limiting factors that reduce realistic risk: the attack is local rather than remote, it needs an existing low-privileged foothold (PR:L), it cannot succeed without the victim approving an elevation prompt, and it is confined to Windows installations older than 4.92.0 - patched versions verify the package signature. |
| Impact | CVSS 4.0 base score is 7.3 (HIGH), but the vector tells a more constrained story than the headline number: AV:L (local), AT:P (an attack requirement must be met), PR:L (attacker already has low-level access), and UI:A (active user interaction required). Exploitation therefore depends on a chain of preconditions - local delivery of a crafted package plus a victim actively approving a Docker-signed UAC elevation prompt - rather than remote, unauthenticated reach. No EPSS score was supplied, the CVE is not listed in CISA KEV, and no proof-of-concept is referenced, so this is 'no public exploit identified at time of analysis.' The core defect (CWE-347, improper signature verification on packages passed to Docker Desktop Installer.exe install -package) is genuinely serious because successful exploitation yields LocalSystem execution with full scope change (SC:H/SI:H/SA:H), but the social-engineering and local-access gating makes this a credible targeted-attack / malicious-insider risk rather than a mass-exploitation priority. Signals are internally consistent - high impact, low likelihood of opportunistic exploitation - so this warrants prompt patching on developer workstations but is not an emergency akin to a remote unauthenticated RCE. Note that no CVSS 3.1 vector or EPSS data was provided for cross-validation; only the 4.0 vector is available. |
| Exploit ScenarioDerived | An attacker who already has local, low-privileged access to a Windows developer workstation (or who socially engineers a user into running a prepared command) places a maliciously crafted installer package on the system and invokes 'Docker Desktop Installer.exe install -package' against it. Because versions before 4.92.0 do not verify the package signature, the attacker's installer actions run as LocalSystem the moment the user approves the legitimately Docker-signed UAC prompt, which appears trustworthy. No public exploit code is referenced, so this scenario is inferred from the description and CVSS vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 09, 2026
Docker Desktop for Windows versions prior to 4.92.0 fail to verify the cryptographic signature of packages supplied via the 'Docker Desktop Installer.exe install -package' command-line option. An attacker who can place a crafted package on the target host and convince a user to approve the Docker-signed UAC elevation prompt can execute arbitrary installer actions as LocalSystem, achieving full system compromise. Although the CVSS 4.0 base score is 7.3 (HIGH), exploitation is constrained: it is a local attack requiring an existing low-privileged foothold and active user interaction; no public exploit code has been identified at time of analysis, and the vendor has released a patch in 4.92.0.
Earlier versions of this analysis (1)
Local privilege escalation in Docker Desktop for Windows before 4.92.0 allows a local user to execute arbitrary installer actions as LocalSystem by supplying a crafted package to the 'install -package' command and convincing a victim to approve a Docker-signed UAC prompt. The vulnerability stems from improper signature verification (CWE-347) of the supplied package. No public exploit code or active exploitation has been identified at time of analysis, but the issue is high severity (CVSS 8.2) and a patch is available in version 4.92.0.
RemediationAI
Upgrade to Docker Desktop for Windows version 4.92.0 or later, which verifies the signature of packages supplied to 'Docker Desktop Installer.exe install -package'; the fix is documented in the release notes at https://docs.docker.com/desktop/release-notes/#4920. If immediate upgrade is not possible, avoid using the 'install -package' command-line option with untrusted packages, and restrict local access to installations of Docker Desktop so that only fully trusted users can place files on the host. Additionally, consider monitoring for suspicious use of the installer command line (e.g., unusual package paths) and remind users to scrutinize UAC prompts, though the Docker-signed nature of the prompt may make this less effective. These compensating controls may disrupt legitimate automated deployment workflows that rely on the -package option.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is rooted in CWE-347 (Improper Verification of Cryptographic Signature). Docker Desktop Installer.exe exposes a command-line interface where the 'install -package' option accepts a package file to perform installation actions. While the installer itself is Docker-signed (triggering a legitimate UAC prompt), it does not validate the digital signature of the supplied package before executing its contents. This allows an attacker to craft a package that, when approved by the user via the Docker-signed UAC prompt, runs arbitrary installer actions with LocalSystem privileges. The affected product is identified by CPE cpe:2.3:a:docker:docker_desktop:*:*:*:*:*:*:*:* (all versions before 4.92.0) and is specific to Windows installations. The flaw is a local privilege escalation vector, as the attacker must already have the ability to deliver the malicious package to the host (AV:L, PR:L) and relies on the user actively approving the elevation prompt (UI:A).
Know when Docker gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Local package delivery with existing low privileges (AV:L/PR:L), success gated on the victim approving the UAC prompt (UI:R), and elevation from user to LocalSystem gives S:C with full C/I/A impact.
Primary rating from Vendor (Docker).
CVSS VectorVendor: Docker
Lifecycle Timeline
3DescriptionCVE.org
Before 4.92.0, Docker Desktop for Windows did not verify the signature of a package supplied to Docker Desktop Installer.exe install -package. An attacker able to provide a crafted package and convince a user to approve the Docker-signed UAC prompt could execute attacker-controlled installer actions as LocalSystem.
Articles & Coverage 1
Executive ViewAI
Docker Desktop for Windows versions prior to 4.92.0 contain a package signature verification flaw that allows a user with an existing low-privileged foothold on a Windows endpoint to escalate to full LocalSystem control by presenting a crafted installer package and obtaining user approval of a legitimate-looking Docker-signed UAC prompt. The exposure is concentrated in engineering and developer workstation populations where Docker Desktop is installed, and a successful exploit yields complete control of the host, including any credentials, source code, and container registry tokens it holds. While exploitation demands local access and user interaction and no public exploit code has been identified at time of analysis, the severity of the resulting compromise warrants prompt remediation across the affected fleet.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
An issue was discovered in Appsmith before 1.52. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
runc through version 1.0-rc6 (used in Docker before 18.09.2) contains a container escape vulnerability that allows attac
Netmaker makes networks with WireGuard. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no a
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
The News & Blog Designer Pack - WordPress Blog Plugin - (Blog Post Grid, Blog Post Slider, Blog Post Carousel, Blog Post
Path traversal in JFrog Artifactory (CWE-22) enables an authenticated low-privilege user to write data outside the inten
Docker 1.3.2 allows remote attackers to execute arbitrary code with root privileges via a crafted (1) image or (2) build
Remote code execution in Gogs through 0.14.2 allows authenticated users (and unauthenticated attackers on default-config
Unauthenticated remote command injection in SGWBOX N3 firmware 2.0.25 lets attackers execute arbitrary operating-system
Remote code execution in Flowise before 3.1.2 allows any authenticated user (or API caller with chatflow view/update per
Remote code execution in NocoBase Workflow Script Node (npm @nocobase/plugin-workflow-javascript) allows authenticated l
Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-c
EUVD-2026-95778
GHSA-r8rf-x7cj-7933
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB