Individual skill
offensive-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAP_SYS_ADMIN, CAP_SYS_PTRACE, and CAP_NET_ADMIN, cgroup v1 notify_on_release escape, runc CVEs such as CVE-2019-5736 and CVE-2024-21626 Leaky Vessels, kernel exploits from within containers, and Dockerfile misconfigurations like --privileged and host namespace sharing. Includes enumeration with capsh, amicontained, deepce, CDK, and nsenter. Maps to MITRE ATT&CK T1611 Escape to Host. Use this skill when the engagement scope includes container breakout, Docker escape, container privilege escalation, host access from container, or when you land inside a containerized environment and need to reach the underlying host.
Skills/container/offensive-container-escape/SKILL.md
Source commit a8de813edc9f66f60d44cfe42d47750e89d9930b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 10,483
- Repository last updated
- Oct 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-ai Repository topic
- claude-skills Repository topic
- redteam Repository topic
- redteam-tools Repository topic
- skills Repository topic
- claude-pt Repository topic
- devops Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytesSKILL.mdcore · 21,739 bytes
Read excerpt
# Container Escape and Breakout
You have a shell inside a container. Your objective is to break out to the underlying host operating system. Container isolation relies on Linux namespaces, cgroups, seccomp profiles, AppArmor/SELinux, and dropped capabilities. Every misconfiguration in these layers is an escape vector. This skill walks you through systematic enumeration, exploitation of common misconfigurations, abuse of exposed runtime sockets, capability-based escapes, cgroup breakouts, and known CVEs against container runtimes.
## Quick Workflow
1. Confirm you are inside a container (check for `.dockerenv`, cgroup entries, PID 1 process).
2. Enumerate capabilities, mounts, namespaces, and sockets with automated tools.
3. Identify the escape vector: privileged mode, socket exposure, dangerous capabilities, cgroup misconfiguration, or vulnerable runtime.
4. Execute the breakout technique matching the vector.
5. Validate host access by reading `/etc/hostname`, checking PID namespace, or writing to host filesystem.
6. Pivot from host access to lateral movement across the cluster or infrastructure.
---