GCP News - 2026-06-18

2026-06-18
最終更新: 2026-08-27 21:31:34 JST

GKE Security Bulletins

GCP-2026-037

詳細を表示

Published: 2026-06-18

Updated: 2026-06-20

Reference: CVE-2026-50195, CVE-2026-53488, CVE-2026-53492, CVE-2026-53489, CVE-2026-47262

2026-06-20 Update: Added GKE patch versions containing the fixes for Container-Optimized OS node images for minor versions 1.35 and 1.36. Patches for Ubuntu node images are still pending and in progress.

2026-06-19 Update: Added GKE patch versions containing the fixes for Container-Optimized OS node images for minor versions from 1.30 to 1.34. Patches for Ubuntu node images and for minor version 1.35 and 1.36 for Container-Optimized OS node images are in progress.

Description Severity

The following vulnerabilities have been discovered in containerd (the GKE container runtime). These vulnerabilities allow attackers with permissions to create Pods to bypass Kubernetes security boundaries and perform host compromise, cache poisoning, and denial of service. While these vulnerabilities are critical in the context of containerd, the requirement to have cluster privileges to create Pods to exploit them means they are considered High according to GKE vulnerability classification.

  • CVE-2026-50195 (Critical): containerd's CRI checkpoint import process fails to validate image references. An attacker with permissions to create Pods can use a crafted checkpoint image to poison the node's local image cache, causing other pods using an IfNotPresent pull policy to execute malicious code.
  • CVE-2026-53488 (Critical): CRI plugin propagates labels from an image config to a container without validation. This may result in executing an arbitrary command on the host.
  • CVE-2026-53492 (Critical): CRI implementation improperly trusts Container Device Interface (CDI) annotations during container restoration. This allows an attacker to inject arbitrary CDI configurations (such as host mounts and device nodes) into restored containers, bypassing resource allocation and device plugin enforcement.
  • CVE-2026-53489 (High): CRI plugin restores container.log without validating a symlinked path, allowing an attacker to read arbitrary host files via kubectl logs.
  • CVE-2026-47262 (Moderate): A vulnerability in containerd allows a maliciously crafted image to cause memory exhaustion (DoS) of the containerd process.

These vulnerabilities affect all GKE configurations using Container-Optimized OS and Ubuntu node images, including GKE Standard and GKE Autopilot clusters.

What should I do?

2026-06-20 Update: The following GKE patch versions contain the fixes for Container-Optimized OS node images for minor versions from 1.30 to 1.36. Upgrade your Container-Optimized OS node pools to the following versions or later:

  • 1.36.0-gke.3545000 or later
  • 1.35.6-gke.1039000 or later
  • 1.34.9-gke.1021000 or later
  • 1.33.12-gke.1267000 or later
  • 1.32.13-gke.1823000 or later
  • 1.31.14-gke.2150000 or later
  • 1.30.14-gke.2726000 or later

Patches for Ubuntu node images are in progress.


Until patch versions are available, use the following mitigation guidelines:

  • Restrict Pod creation permissions (create pods in Kubernetes RBAC) only to trusted users, as critical vectors require pod creation or restoration capabilities.
  • Avoid using IfNotPresent or Never image pull policies for untrusted or critical workloads; use Always to force verification against a trusted registry.
  • Restrict or monitor use of checkpointing/restoration features in your clusters.
High