Information Exposure Through Log Files The advisory has been revoked - it doesn't affect any version of package kubeflow  (opens in a new tab)


Threat Intelligence

EPSS
0.52% (43rd percentile)

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-KUBEFLOW-10627273
  • published4 Jul 2025
  • disclosed7 Dec 2020

Introduced: 7 Dec 2020

CVE-2020-8565  (opens in a new tab)
CWE-532  (opens in a new tab)

Amendment

The Chainguard security team deemed this advisory irrelevant for Chainguard:latest.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kubeflow package and not the kubeflow package as distributed by Chainguard.

In Kubernetes, if the logging level is set to at least 9, authorization and bearer tokens will be written to log files. This can occur both in API server logs and client tool output like kubectl. This affects <= v1.19.3, <= v1.18.10, <= v1.17.13, < v1.20.0-alpha2.