Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-15558 high CVSS 8.0

Vulnerability in docker-cli (CVE-2025-15558)

Summary

Vulnerability in docker-cli (CVE-2025-15558). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 29.2.1 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-15558 has been found in docker-cli.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: upgrade docker-cli to 29.2.1 or later.
If unsure, ask your IT team or search "docker-cli CVE-2025-15558" on the vendor's site.

CVE-2025-15558 (docker-cli) — CWE-427 / CVSS v3 8.0
Attack vector: remote (network-reachable)
Patched: 29.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-427) exists in docker-cli.

📍 Affected scope

Check the vendor advisory for the affected versions of docker-cli.

🔥 Severity

Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 29.2.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'docker-cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'docker-cli' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で docker-cli を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade docker-cli to 29.2.1

    ステージング環境で 29.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami docker-cli
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"29.2.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details