Kubernetes · Kubernetes · published 2026-10-26
CVE-2026-2270StatefulSet and ControllerRevision write permissions allow cross-namespace pod creation
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-2270 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 38% of all CVEs. This Kubernetes vulnerability: CVSS 5.9 (v3.1), a successful attack gives total control of the component. Fixed upstream in Kubernetes kubelet 1.37.1, kubelet 1.36.5, kubelet 1.35.9, kubelet 1.34.12 (+4 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Kubernetes kubelet 1.37.1, kubelet 1.36.5, kubelet 1.35.9, kubelet 1.34.12, kube-controller-manager 1.37.1, kube-controller-manager 1.36.5, kube-controller-manager 1.35.9, kube-controller-manager 1.34.12.
Patch events
OrchestrationKubernetes
Kubernetes security fixes: 2 CVEs
Upgrade to
kubelet 1.37.1kubelet 1.36.5kubelet 1.35.9kubelet 1.34.12kube-controller-manager 1.37.1kube-controller-manager 1.36.5kube-controller-manager 1.35.9kube-controller-manager 1.34.12Why: Vendor security release for server software (most severe: CVE-2026-2270).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (38th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.9 (v3.1)CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Kubernetes Kubernetes
v1.34.0throughv1.34.11(affected)v1.35.0throughv1.35.8(affected)v1.36.0throughv1.36.4(affected)v1.37.0throughv1.37.0(affected)
Description (from the CVE record)#
A confused deputy attack exists in the StatefulSet controller that allows a user with namespace-scoped write permissions on StatefulSet and ControllerRevision objects to create a cross-namespace pod. An attacker exploiting this vulnerability would have full control over the resulting pod’s metadata and specification, including namespace selection. Note that the cross-namespace pod will be immediately deleted by the garbage collector unless the attacker is able to construct a valid StatefulSet OwnerReference. This would require referencing the UID of an existing StatefulSet in the victim’s namespace.
Quoted from the CVE Program record.