CVE-2019-11243: GO-2025-3645 - Kubernetes did not effectively clear service account credentials in k8s.io/kubernetes

CVE-2019-11243 · Severity: low · CVSS 3.1 · Published 2025-05-05

Kubernetes did not effectively clear service account credentials in k8s.io/kubernetes

Technologies: k8s.io/kubernetes (Go). Vendors: Go.

Quick answers

Is CVE-2019-11243 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-11243 being exploited in the wild.
How severe is CVE-2019-11243?
Low severity, with a CVSS score of 3.1, published 5 May 2025.
Which products and versions are affected?
k8s.io/kubernetes (Go) SEMVER:introduced=1.12.0,fixed=1.12.5, SEMVER:introduced=1.12.0,fixed=1.12.5,introduced=1.13.0,fixed=1.13.1.
Is there a fix for CVE-2019-11243?
Yes. k8s.io/kubernetes (Go): upgrade to 1.12.5, 1.13.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-11243?
Check whether you run k8s.io/kubernetes (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • k8s.io/kubernetes (Go): upgrade to 1.12.5, 1.13.1 or later
    go get k8s.io/kubernetes@v1.13.1

Affected products

  • k8s.io/kubernetes (Go) SEMVER:introduced=1.12.0,fixed=1.12.5, SEMVER:introduced=1.12.0,fixed=1.12.5,introduced=1.13.0,fixed=1.13.1

Identifiers

  • CVE-2019-11243
  • GHSA-gc2p-g4fg-29vh
  • GO-2025-3645

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.