LiveActive security incident?Get immediate response
CVE Record

CVE-2025-15558: Docker Desktop Docker Plugins Uncontrolled Search Path Element Local Privilege Escalation Vulnerability

Docker CLI for Windows searches for plugin binaries in C:\ProgramData\Docker\cli-plugins, a directory that does not exist by default. A low-privileged attacker can create this directory and place malicious CLI plugin binaries (docker-compose.exe, docker-buildx.exe, etc.) that are executed when a victim user opens Docker Desktop or invokes Docker CLI plugin features, and allow privilege-escalation if the docker CLI is executed as a privileged user. This issue affects Docker CLI: through 29.1.5 and Windows binaries acting as a CLI-plugin manager using the github.com/docker/cli/cli-plugins/manager https://pkg.go.dev/github.com/docker/cli@v29.1.5+incompatible/cli-plugins/manager  package, such as Docker Compose. This issue does not impact non-Windows binaries, and projects not using the plugin-manager code.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

On Windows, Docker CLI can look for plugin programs in a global folder that may not exist by default. A low-privileged local attacker could create that folder and place malicious plugin binaries there. If a more privileged user later opens Docker Desktop or uses Docker plugin features, those binaries could run with that user’s privileges.

Executive priority

Treat this as high priority for Windows developer fleets and privileged build hosts. It is not remotely exploitable from the supplied evidence, but it can turn a low-privileged local foothold into administrator-level impact when Docker is used elevated.

Technical view

CVE-2025-15558 is a CWE-427 uncontrolled search path issue in Docker CLI plugin discovery on Windows. The reported path is C:\ProgramData\Docker\cli-plugins. Sources describe Docker CLI through 29.1.5 and Windows binaries using Docker’s cli-plugins manager as in scope; non-Windows binaries and projects not using that code are out of scope.

Likely exposure

Exposure is mainly Windows developer or build workstations running Docker Desktop, Docker CLI, or related Windows binaries using Docker’s CLI plugin manager. Risk increases where Docker commands are run elevated or by administrator accounts. Non-Windows deployments are not indicated as affected in the provided sources.

Exploitation context

The CVSS vector is local, low complexity, low privilege required, and user interaction required. The bundle marks KEV as false, and no cited source in the bundle establishes active exploitation. This should be treated as plausible local privilege escalation, not confirmed in-the-wild exploitation.

Researcher notes

There is some version ambiguity in the supplied bundle: the description says Docker CLI through 29.1.5, while the affected metadata lists Docker CLI 29.2.0 as affected and Compose 5.1.0 as unaffected. Validate final affected and fixed versions from Docker sources before enforcement.

Mitigation direction

  • Review Docker release notes and apply the vendor-fixed Docker Desktop or Docker CLI version.
  • Prioritize Windows systems where Docker CLI is run with administrative privileges.
  • Restrict creation and modification of C:\ProgramData\Docker\cli-plugins where feasible.
  • Audit third-party Windows binaries that use Docker’s cli-plugins manager package.
  • If no fixed version is confirmed, follow Docker’s advisory and release guidance.

Validation and detection

  • Inventory Windows hosts with Docker Desktop, Docker CLI, Docker Compose, or Docker plugin-manager consumers.
  • Check installed Docker CLI versions against vendor release notes and the CVE record.
  • Inspect C:\ProgramData\Docker\cli-plugins permissions and unexpected plugin binaries.
  • Confirm whether users or automation run Docker commands elevated.
  • Monitor endpoint telemetry for unexpected Docker plugin binary execution from ProgramData.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-427: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-15558 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H1.35.9redhat-SADP
7CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:N/R:UDocker

Vulnerability scoring details

Base CVSS 4.0 score

7High
CVSS 4.0 vector shape for CVE-2025-15558Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:N/R:U

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPdocker/cli: Docker CLI for Windows: Privilege escalation via malicious plugin binaries
other:Red Hat severity ratingcvssV3_1
  • 2026-03-04T17:01:09.062Z: Reported to Red Hat.
  • 2026-03-04T16:14:32.045Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DockerDocker CLI29.2.0affected
DockerCompose5.1.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-427 · source CWE mapping

Uncontrolled Search Path Element

Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.