Docker CLI leaks private registry credentials to registry-1.docker.io

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N

EPSS

• CVE-2021-41092: 1.65% estimated exploitation activity in the next 30 days; percentile 76.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A bug was found in the Docker CLI where running docker login my-private-registry.example.com with a misconfigured configuration file (typically ~/.docker/config.json) listing a credsStore or credHelpers that could not be executed would result in any provided credentials being sent to registry-1.docker.io rather than the intended private registry. Patches This bug has been fixed in Docker CLI 20.10.9. Users should update to this version as soon as possible. Workarounds Ensure that any configured credsStore or credHelpers entries in the configuration file reference an installed credential helper that is executable and on the PATH. For more information If you have any questions or comments about this advisory: Open an issue Email us at security@docker.com if you think you’ve found a security bug

Published by the source

10 Jun 2024, 18:38 UTC

Last modified by the source

5 Jul 2024, 21:43 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-99pg-grm5-qq3v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-41092

Advisory: Docker CLI leaks private registry credentials to registry-1.docker.io
IDs: CVE-2021-41092, GHSA-99pg-grm5-qq3v
Record: https://patchnext.com/advisories/cve-2021-41092 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/docker/cli 20.10.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/docker/cli: affected < 20.10.9; fixed in 20.10.9

## Suggested inspection (read-only)
- Go github.com/docker/cli: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/docker/cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-99pg-grm5-qq3v (GitHub-reviewed advisory GHSA-99pg-grm5-qq3v lists affected ranges: Go github.com/docker/cli >=0 <20.10.9)

Commands are suggestions: review each one before running it.