CVE-2019-11245: kubelet-started container uid changes to root after first restart or if image is already pulled to the node
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: k8s.io/kubernetes (Go) 1.13.7, 1.14.3; k8s.io/kubernetes/cmd/kubelet (Go) 1.13.7, 1.14.3; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250807T150727-1.1.
- Severity is disputed: the assigning authority (CNA) scores it 4.9, NVD 7.8.
Low priority for now. Upgrade to k8s.io/kubernetes (Go) 1.13.7, 1.14.3; k8s.io/kubernetes/cmd/kubelet (Go) 1.13.7, 1.14.3; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20250807T150727-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Aug 28, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 49th percentile
- CWE
- CWE-703
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- 7.8
- CNA · kubernetes
- 4.9
- 2.9 point gap
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| kubernetes | kubernetes | cpe:2.3:a:kubernetes:kubernetes |
Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.
Kubernetes Kubernetes
- v1.13.6, v1.14.2affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kubernetes kubernetes1.13.6
- kubernetes kubernetes1.14.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | k8s.io/kubernetes | from 1.13.0 · before 1.13.7 | 1.13.7 |
| Go | k8s.io/kubernetes | from 1.14.0 · before 1.14.3 | 1.14.3 |
| Go | k8s.io/kubernetes/cmd/kubelet | from 1.13.0 · before 1.13.7 | 1.13.7 |
| Go | k8s.io/kubernetes/cmd/kubelet | from 1.14.0 · before 1.14.3 | 1.14.3 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250807T150727-1.1 | 0.0.20250807T150727-1.1 |
Same product
kubernetes: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1002105In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in…65This week
- CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port55Plan
- CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2019-11243Apr 22, 2019 · In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials…33Monitor
- ← EarlierCVE-2019-11244Apr 22, 2019 · kubectl creates world-writeable cached schema files20Monitor
- Later →CVE-2019-11246Aug 28, 2019 · kubectl cp allows symlink directory traversal27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:k8s.io/kubernetes | 1.13.7 | Package registry (OSV) |
| Go:k8s.io/kubernetes | 1.14.3 | Package registry (OSV) |
| Go:k8s.io/kubernetes/cmd/kubelet | 1.13.7 | Package registry (OSV) |
| Go:k8s.io/kubernetes/cmd/kubelet | 1.14.3 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250807T150727-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-703 · Improper Check or Handling of Exceptional ConditionsCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.