Kubelet Incorrect Privilege Assignment

Exploitation

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

CVSS

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

EPSS

• CVE-2019-11245: 0.60% estimated exploitation activity in the next 30 days; percentile 48.72 (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 kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit runAsUser attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified mustRunAsNonRoot: true, the kubelet will refuse to start the container as root. If the pod did not specify mustRunAsNonRoot: true, the kubelet will run the container as uid 0.

Published by the source

24 Apr 2024, 20:03 UTC

Last modified by the source

10 Jun 2024, 19:33 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r76g-g87f-vw8f

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

# Patch Next advisory brief: CVE-2019-11245

Advisory: Kubelet Incorrect Privilege Assignment
IDs: CVE-2019-11245, GHSA-r76g-g87f-vw8f
Record: https://patchnext.com/advisories/cve-2019-11245 (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.9)
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/cmd/kubelet 1.14.3, 1.13.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go k8s.io/kubernetes/cmd/kubelet: affected >= 1.14.0, < 1.14.3; >= 1.13.0, < 1.13.7; fixed in 1.14.3, 1.13.7

## Suggested inspection (read-only)
- Go k8s.io/kubernetes/cmd/kubelet: 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/cmd/kubelet.
- 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-r76g-g87f-vw8f (GitHub-reviewed advisory GHSA-r76g-g87f-vw8f lists affected ranges: Go k8s.io/kubernetes/cmd/kubelet >=1.14.0 =1.13.0 <1.13.7)

Commands are suggestions: review each one before running it.