CVE-2025-15558 Affecting cosign-fips package, versions <3.0.5-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-COSIGNFIPS-15437816
  • published6 Mar 2026
  • disclosed4 Mar 2026

Introduced: 4 Mar 2026

NewCVE-2025-15558  (opens in a new tab)

How to fix?

Upgrade Chainguard cosign-fips to version 3.0.5-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cosign-fips package and not the cosign-fips package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.