Skip to content

chore(deps): update module github.com/docker/cli to v29 [security]#333

Open
renovate-rancher[bot] wants to merge 1 commit intomainfrom
renovate/go-github.com-docker-cli-vulnerability
Open

chore(deps): update module github.com/docker/cli to v29 [security]#333
renovate-rancher[bot] wants to merge 1 commit intomainfrom
renovate/go-github.com-docker-cli-vulnerability

Conversation

@renovate-rancher
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
github.com/docker/cli v28.5.1+incompatiblev29.2.0+incompatible age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

GitHub Vulnerability Alerts

CVE-2025-15558

This issue affects Docker CLI through 29.1.5

Impact

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 v29.1.5 (fixed in v29.2.0). It impacts Windows binaries acting as a CLI plugin manager via the github.com/docker/cli/cli-plugins/manager package, which is consumed by downstream projects such as Docker Compose.

Docker Compose became affected starting in v2.31.0, when it incorporated the relevant CLI plugin manager code (see https://github.com/docker/compose/pull/12300), and is fixed in v5.1.0.

This issue does not impact non-Windows binaries or projects that do not use the plugin manager code.

Patches

Fixed version starts with 29.2.0

This issue was fixed in docker/cli@1375933 (https://github.com/docker/cli/pull/6713), which removed %PROGRAMDATA%\Docker\cli-plugins from the list of paths used for plugin-discovery on Windows.

Workarounds

None

Resources

Credits

Nitesh Surana (niteshsurana.com) of Trend Research of TrendAI


Release Notes

docker/cli (github.com/docker/cli)

v29.2.0+incompatible

Compare Source

v29.1.5+incompatible

Compare Source

v29.1.4+incompatible

Compare Source

v29.1.3+incompatible

Compare Source

v29.1.2+incompatible

Compare Source

v29.1.1+incompatible

Compare Source

v29.1.0+incompatible

Compare Source

v29.0.4+incompatible

Compare Source

v29.0.3+incompatible

Compare Source

v29.0.2+incompatible

Compare Source

v29.0.1+incompatible

Compare Source

v29.0.0+incompatible

Compare Source

v28.5.2+incompatible

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@renovate-rancher renovate-rancher bot changed the title chore(deps): update module github.com/docker/cli to v29 [security] chore(deps): update module github.com/docker/cli to v29 [security] - autoclosed Mar 9, 2026
@renovate-rancher renovate-rancher bot closed this Mar 9, 2026
@renovate-rancher renovate-rancher bot deleted the renovate/go-github.com-docker-cli-vulnerability branch March 9, 2026 05:08
@renovate-rancher renovate-rancher bot changed the title chore(deps): update module github.com/docker/cli to v29 [security] - autoclosed chore(deps): update module github.com/docker/cli to v29 [security] Mar 10, 2026
@renovate-rancher renovate-rancher bot reopened this Mar 10, 2026
@renovate-rancher renovate-rancher bot force-pushed the renovate/go-github.com-docker-cli-vulnerability branch 2 times, most recently from 0023e0e to 476f8cc Compare March 10, 2026 04:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants