CVE-2026-2270

Description

A flaw was found in Kubernetes kube-controller-manager. The StatefulSet controller restores ControllerRevision data onto the whole StatefulSet object, including metadata. A user with namespace-scoped write access to StatefulSet and ControllerRevision can cause the controller to create a pod in another namespace. That pod is deleted by garbage collection unless the attacker can name the UID of a StatefulSet in the target namespace.

Statement

The attacker needs write on both StatefulSet and ControllerRevision in some namespace, plus a way to make the controller apply that revision. Default OpenShift edit and admin roles do not grant ControllerRevision create/update (only get/list/watch), matching upstream Kubernetes. A custom Role or cluster-admin is required. For the pod to survive, the attacker must also know a StatefulSet UID in the victim namespace.

Mitigation

Do not grant create/update/patch on ControllerRevision to users or service accounts that only need to manage StatefulSets.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.9N/A5.9
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredHighN/AHigh
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactNoneN/ANone

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

cve.org: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Understanding the Weakness (CWE)

Confidentiality,Integrity,Availability,Access Control

Technical Impact: Modify Memory; Read Memory; Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity; Bypass Protection Mechanism; Other

A common weakness that can exist in such protection schemes is that access controls or policies are not granular enough, which renders the control policy too broad, because it allows accesses from unauthorized agents to security-sensitive assets. This condition allows agents beyond trusted agents to access assets and could lead to a loss of functionality or the ability to set up the device securely. This further results in security risks from leaked, sensitive, key material to modification of device configuration.

Frequently Asked Questions

Want to get errata notifications? Sign up here.