CVE-2019-11245

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. Limited direct impact.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2019-08-29 01:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:12 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 4.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2019-08-29 01:15 UTC

Last modified

2026-06-17 02:12 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-703

Record status

Modified

Affected

• Kubernetes 1.13.6
• Kubernetes 1.14.2

Attack profile CVSS 3.0 · 4.9

Attack vector

Local

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-11245.md and follow it. Check whether this project is affected by CVE-2019-11245. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge