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-53489 — containerd checkpoint restore symlink allows host file read

HIGHCVE-2026-53489GHSA-rgh6-rfwx-v388

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

A bug in containerd's CRI plugin causes container.log to be restored from a checkpoint image without validating whether the path is a symlink. An attacker who can supply a crafted checkpoint image can use this to make containerd follow a symlink that points to an arbitrary file on the host, which is then exposed via kubectl logs.

Impact

An attacker with permissions to create pods and supply a crafted checkpoint image can read arbitrary files on the node host filesystem by causing container.log to be a symlink to any readable path. Because the file content is surfaced through kubectl logs, no direct node access is required after the checkpoint is restored. Sensitive files such as service account tokens, certificates, and configuration files in the host's filesystem could be disclosed to any user who can run kubectl logs against the affected pod.

Detection

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

containerd --version

Inspect checkpoint archives before use for symlinked container.log entries. Audit kubectl logs access and checkpoint restore operations in the cluster's audit log to detect potential exploitation attempts.

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

As a workaround, ensure that only trusted images and checkpoints are used. Restricting which users can perform checkpoint/restore operations and limiting pod creation to trusted users reduces the risk on clusters that cannot upgrade immediately.

References

GHSA-rgh6-rfwx-v388 — GitHub Security Advisory
NVD CVE-2026-53489 — National Vulnerability Database

Affected versions

Patched versions

References

Summary​

Impact​

Detection​

Mitigation​

Related Security Guidance​

References​

Summary

Impact

Detection

Mitigation

Related Security Guidance

References