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-50195 — containerd checkpoint import enables image tag poisoning

MEDIUMCVE-2026-50195GHSA-cvxm-645q-p574

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 checkpoint import process fails to validate the image references specified within a checkpoint image's configuration. An attacker with permissions to create pods can use a crafted checkpoint image to force containerd to pull a malicious image and assign it an arbitrary local tag, thereby poisoning the node's local image cache.

Impact

If other pods on the same node subsequently attempt to use the poisoned tag with an IfNotPresent (or Never) pull policy, they will execute the attacker's malicious image instead of the legitimate one. This can lead to a compromise of the affected pods, allowing the attacker to execute arbitrary code under the victim pod's identity. The attack requires permissions to create pods and the ability to supply a crafted checkpoint image, but once the local image cache is poisoned the impact extends to any workload on that node referencing the targeted tag.

Detection

Review audit logs for unexpected pod checkpoint restore operations and cross-reference the image references in checkpoint archives against the cluster's allowed image registries. 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. Confirm the running version:

containerd --version

Monitor for image pull events that originate from checkpoint restore paths, particularly where the resulting local tag does not match the expected registry source.

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, restrict pod creation to trusted users and allow only trusted images to be pulled. Limiting access to checkpoint/restore operations reduces the attack surface on clusters that cannot upgrade immediately.

References

GHSA-cvxm-645q-p574 — GitHub Security Advisory
NVD CVE-2026-50195 — National Vulnerability Database

Affected versions

Patched versions

References

Summary​

Impact​

Detection​

Mitigation​

Related Security Guidance​

References​

Summary

Impact

Detection

Mitigation

Related Security Guidance

References