Kubernetes Sensitive Information leak via Log File

Exploitation

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

CVSS

4.7 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2020-8564: 0.47% estimated exploitation activity in the next 30 days; percentile 40.47 (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.

In Kubernetes clusters using a logging level of at least 4, processing a malformed docker config file will result in the contents of the docker config file being leaked, which can include pull secrets or other registry credentials. This affects < v1.19.3, < v1.18.10, < v1.17.13.

Published by the source

6 Feb 2023, 23:27 UTC

Last modified by the source

20 May 2024, 19:26 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8mjg-8c8g-6h85

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

# Patch Next advisory brief: CVE-2020-8564

Advisory: Kubernetes Sensitive Information leak via Log File
IDs: CVE-2020-8564, GHSA-8mjg-8c8g-6h85
Record: https://patchnext.com/advisories/cve-2020-8564 (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 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: k8s.io/kubernetes 1.20.0-alpha.1; github.com/kubernetes/kubernetes 1.19.3, 1.18.10, 1.17.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go k8s.io/kubernetes: affected < 1.20.0-alpha.1; fixed in 1.20.0-alpha.1
- Go github.com/kubernetes/kubernetes: affected >= 1.19.0, < 1.19.3; >= 1.18.0, < 1.18.10; < 1.17.13; fixed in 1.18.10, 1.19.3, 1.17.13

## Suggested inspection (read-only)
- Go k8s.io/kubernetes: check the installed version with your package manager.
- Go github.com/kubernetes/kubernetes: 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 k8s.io/kubernetes, github.com/kubernetes/kubernetes.
- 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-8mjg-8c8g-6h85 (GitHub-reviewed advisory GHSA-8mjg-8c8g-6h85 lists affected ranges: Go github.com/kubernetes/kubernetes >=1.19.0 =1.18.0 =0 =0 <1.20.0-alpha.1)

Commands are suggestions: review each one before running it.