CVE-2019-11245 - CVE House
Back to Database
Status published Medium CVE-2019-11245

kubelet-started container uid changes to root after first restart or if image is already pulled to the node

Vulnerability Description

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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2019-11245

Credits & Attribution

No credits recorded in the NVD database.

References

More from Kubernetes

View All →
CVE-2025-9708
Kubernetes C# Client: improper certificate validation in custom CA mode may lead to man-in-the-middle attacks
Medium 6.8
CVE-2025-7445
Kubernetes secrets-store-sync-controller discloses service account tokens in logs
Medium 6.5
CVE-2025-7342
VM images built with Kubernetes Image Builder Nutanix or OVA providers use default credentials for Windows images if user did not override
High 7.5
CVE-2025-5187
Nodes can delete themselves by adding an OwnerReference
Medium 6.7
CVE-2025-4563
Nodes can bypass dynamic resource allocation authorization checks
Low 2.7

Affected Vendor

Affected Software

Kubernetes
Vulnerable Versions:
v1.13.6, v1.14.2

Timeline

Official Publish: August 29th, 2019
Last Modified: September 16th, 2024
Added to House: July 20th, 2026

CVSS Vectors

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

Weaknesses (CWE)

CWE-703

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.