What is Kubernetes security?

Kubernetes security encompasses the practices, tools, and configurations used to protect Kubernetes clusters, workloads, and data. It includes authentication, authorization (RBAC), network policies, pod security standards, secrets management, and runtime security.

What is the CKS certification?

The Certified Kubernetes Security Specialist (CKS) is a CNCF certification that validates expertise in securing Kubernetes clusters. It covers cluster setup and hardening, system hardening, minimizing microservice vulnerabilities, and supply chain security.

What are Kubernetes network policies?

Network policies are Kubernetes resources that control pod-to-pod and pod-to-external traffic. They act as a firewall for your cluster, allowing you to specify which pods can communicate with each other based on labels, namespaces, and ports.

What are Pod Security Standards?

Pod Security Standards (PSS) are predefined security profiles that define different levels of pod security restrictions: Privileged (unrestricted), Baseline (minimally restrictive to prevent known privilege escalations), and Restricted (heavily restricted following security best practices).

What is RBAC in Kubernetes?

Role-Based Access Control (RBAC) is a Kubernetes authorization mechanism that regulates access to resources based on user roles. It uses Role, ClusterRole, RoleBinding, and ClusterRoleBinding resources to define and assign permissions to users and service accounts.

How do I secure etcd in Kubernetes?

Secure etcd by enabling encryption at rest for secrets, using TLS for client-server communication, restricting access to etcd endpoints via firewall rules, enabling authentication, and running regular backups. etcd stores all cluster data including secrets.

What is a container escape attack?

A container escape attack occurs when a process breaks out of container isolation to access the host system or other containers. Common vectors include privileged containers, hostPath mounts, and kernel exploits. Mitigate with Pod Security Standards and seccomp profiles.

What tools are used for Kubernetes security scanning?

Popular Kubernetes security tools include Trivy (vulnerability scanning), Falco (runtime security), kube-bench (CIS benchmarks), OPA Gatekeeper and Kyverno (policy enforcement), Kubescape (security posture), and Cosign (image signing).

CVE-2026-53492 — containerd CRI CDI annotation smuggling in checkpoint restore

HIGHCVE-2026-53492GHSA-33vj-92qq-66hc

Affected projects: containerd
Disclosed: June 18, 2026
Last updated: October 25, 2026

Affected versions

Project	Vulnerable range
github.com/containerd/containerd/v2	`>= 2.1.0, < 2.1.9`
github.com/containerd/containerd/v2	`>= 2.2.0, < 2.2.5`
github.com/containerd/containerd/v2	`>= 2.3.0, < 2.3.2`

Patched versions

Project	Fixed in
github.com/containerd/containerd/v2	`2.1.9`
github.com/containerd/containerd/v2	`2.2.5`
github.com/containerd/containerd/v2	`2.3.2`

References

Summary

containerd's CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement by injecting arbitrary CDI edits into the restored container.

Impact

Successful exploitation allows a user with pod creation permissions to inject arbitrary CDI edits — such as device nodes and host mounts — into a restored container by embedding crafted CDI annotations in a checkpoint image. This effectively bypasses Kubernetes device plugin enforcement and resource allocation controls. Environments where CDI is disabled or that lack sensitive device specifications in the CDI host directories (/etc/cdi and /var/run/cdi) are not affected. Recreating existing containers restored from untrusted checkpoints may be necessary to remove smuggled configuration.

Detection

Nodes running containerd v2.1.0–v2.1.8, v2.2.0–v2.2.4, or v2.3.0–v2.3.1 with CDI enabled are in the affected version range. Verify the running version and CDI configuration:

containerd --version

Check for CDI specifications in the host CDI directories:

ls /etc/cdi /var/run/cdi 2>/dev/null

If CDI specifications are present for sensitive devices, audit checkpoint restore operations for containers that gained unexpected device access. Review checkpoint archive annotations for CDI-related entries before restoring from untrusted sources.

Mitigation

Upgrade to one of the patched containerd releases:

containerd v2.3.x: upgrade to v2.3.2 or later
containerd v2.2.x: upgrade to v2.2.5 or later
containerd v2.1.x: upgrade to v2.1.9 or later

If CDI capabilities are not required on the node, removing or temporarily relocating host CDI specifications from /etc/cdi and /var/run/cdi eliminates the reachability of this vulnerability. Restrict checkpoint image restoration to trusted sources as an additional control. Recreate any containers that were restored from untrusted checkpoint images to remove potentially smuggled CDI configuration.

References

GHSA-33vj-92qq-66hc — GitHub Security Advisory
NVD CVE-2026-53492 — National Vulnerability Database

Affected versions

Patched versions

References

Summary​

Impact​

Detection​

Mitigation​

Related Security Guidance​

References​

Summary

Impact

Detection

Mitigation

Related Security Guidance

References