Container Escape
Also called Container breakout.
Breaking out of a container's isolation to reach the host or other workloads.
What it is
An attack that defeats the isolation boundary of a container to gain code execution on the underlying host or access to neighboring containers. It typically exploits misconfiguration, excessive privileges, or a runtime vulnerability.
Why it matters
A successful escape collapses the boundary defenders rely on, exposing every workload on the node, so detecting and preventing escape conditions is a top container-security priority.
In practice
An analyst confirms the attacker escaped a container by abusing a writable host path, then read secrets belonging to unrelated pods on the same node.
What to look for
- Containers running privileged or with host mounts such as the Docker socket.
- Processes in a container accessing host namespaces or kernel interfaces.
- Unexpected host processes spawned from container runtimes.
Common mistake
Treating containers as a security boundary by default. Without hardening they share the host kernel.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Trivy Open source
Scans images, file systems and code for known vulnerabilities and secrets.
-
Falco Open source
Detects suspicious behavior inside running containers and Kubernetes.
-
Sigstore Open source
Signs and verifies software artifacts so you can prove where a build came from.
-
CrowdStrike Falcon Cloud Security Commercial
Protects cloud workloads and containers, from build to runtime.
Read next
- Privileged Container: A container run with host-level capabilities that erase most isolation.
- Pod Security: Constraints that limit the privileges and host access a pod may request.