k8s.io/client-go (Go)

Advisories

Latest version

—

License

—

OpenSSF Scorecard

—

How to fix

Upgrading to 0.20.0-alpha.2 or later clears every advisory below that has a fix.

Upgrade commands

go get k8s.io/client-go@v0.20.0-alpha.2 && go mod tidy

Known vulnerabilities

Advisory	Severity	Affected	Fixed in
GHSA-8cfg-vx93-jvxw Kubernetes client-go vulnerable to Sensitive Information Leak via Log File	Medium EPSS 0.52%	`>= 0.19.0, < 0.19.6`	`0.19.6`
GHSA-8cfg-vx93-jvxw Kubernetes client-go vulnerable to Sensitive Information Leak via Log File	Medium EPSS 0.52%	`>= 0.20.0-alpha.0, < 0.20.0-alpha.2`	`0.20.0-alpha.2`
GHSA-8cfg-vx93-jvxw Kubernetes client-go vulnerable to Sensitive Information Leak via Log File	Medium EPSS 0.52%	`>= 0.18.0, < 0.18.14`	`0.18.14`
GHSA-8cfg-vx93-jvxw Kubernetes client-go vulnerable to Sensitive Information Leak via Log File	Medium EPSS 0.52%	`< 0.17.16`	`0.17.16`
GHSA-8cfg-vx93-jvxw Kubernetes client-go vulnerable to Sensitive Information Leak via Log File	Medium EPSS 0.52%	`< 0.20.0-alpha.2`	`0.20.0-alpha.2`
GHSA-jmrx-5g74-6v2f Kubernetes client-go library logs may disclose credentials to unauthorized users	Medium EPSS 1.77%	`< 0.17.0`	`0.17.0`
GHSA-jmrx-5g74-6v2f Kubernetes client-go library logs may disclose credentials to unauthorized users	Medium EPSS 1.77%	`< 0.17.0`	`0.17.0`

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor