NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2019-11250 — client-go

MEDIUMFix: kubernetes/kubernetes#81330

CVE-2019-11250 is a medium-severity (CVSS 6.5) CWE-532 vulnerability in k8s.io/client-go. A fix is available for k8s.io/client-go — see the affected versions and patch details below.

Kubernetes client-go library logs may disclose credentials to unauthorized users

Also known asGHSA-jmrx-5g74-6v2fGO-2021-0065
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.31%0.96%1.61%2.27%0.8%1.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹k8s.io/client-go🐹k8s.io/kubernetes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The Kubernetes client-go library logs request headers at verbosity levels of 7 or higher. This can disclose credentials to unauthorized users via logs or command output. Kubernetes components (such as kube-apiserver) prior to v1.16.0, which make use of basic or bearer token authentication, and run at high verbosity levels, are affected.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gok8s.io/client-goall versions0.17.0go get k8s.io/client-go@v0.17.0
🐹Gok8s.io/kubernetesall versions1.16.0-beta.1go get k8s.io/kubernetes@v1.16.0-beta.1

Affected Products

2 products · 10 configurations
Application
kuberneteskubernetes
< 1.15.3
3 versions
1.15.31.15.41.16.0
Application
openshift container platformredhat
2 versions
3.114.1

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/client-go, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update k8s.io/client-go to 0.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-11250 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 3.11atomic-openshift-0:3.11.157-1.git.0.dfe38da.el7RHSA-2019:4052
Red Hat OpenShift Container Platform 4.1openshift-0:4.1.27-201912021146.git.0.a40116f.el8_0RHSA-2019:4087

Frequently Asked Questions

The Kubernetes client-go library logs request headers at verbosity levels of 7 or higher. This can disclose credentials to unauthorized users via logs or command output. Kubernetes components (such as kube-apiserver) prior to v1.16.0, which make use of basic or bearer token authentication, and run at high verbosity levels, are affected.
O3 Security · Impact-Aware SCA

Is CVE-2019-11250 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-11250: client-go — Fixed in 0.17.0