cloud-container-escape
Break out of a container to the host. Load when you have a shell in a container/pod and want the node: privileged container, mounted docker.sock, dangerous capabilities, hostPath, or "escape the container". Signals: /.dockerenv, cgroup shows docker/k8s, CAP_SYS_ADMIN, mounted socket.
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/cloud-container-escapeWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagec170c1f6…cdbeeb31
c170c1f6a66b…012dcdbeeb311 file · 1.2 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-container-escape@ee0e0c5
On this page
When it applies
You have code execution inside a container and want the underlying host (and from there, other containers / the cluster / cloud creds).
Why it works
Containers are isolation by configuration, not a hard boundary. Privileged mode, extra capabilities, mounted host resources, or an exposed Docker socket give processes inside the container direct control over the host kernel/daemon.
Method
- Confirm & enumerate:
/.dockerenv,/proc/1/cgroup; runamicontained/deepceto list capabilities, seccomp, and mounts. - Exploit the misconfig:
- Docker socket mounted (
/var/run/docker.sock):docker -H unix://... run -v /:/host ...→ mount host FS as root → escape. - Privileged / CAP_SYS_ADMIN: mount the host disk, or use the classic
release_agentcgroup notify_on_release trick to run a command on the host. - hostPath / host mounts: write to host filesystem (cron, ssh keys, kubelet config).
- hostPID: access host processes;
nsenterinto PID 1's namespaces.
- Docker socket mounted (
- From the host: grab cloud metadata creds (→
cloud-imds-ssrf), pivot to other containers/nodes (→cloud-kubernetes).
Gotchas
- Enumerate capabilities/mounts first — the escape depends entirely on which misconfig exists.
- Kernel-exploit escapes are last-resort and risky on live targets; prefer the config-based paths.
- On bug bounty, a proven mount of the host FS is enough — don't disrupt the node.
Verify success
Command execution or file read/write on the host (outside the container namespace) — e.g. host
/etc/shadow, other containers, or the kubelet/cloud creds.
References
deepce/amicontained; "Understanding Docker container escapes" (Trail of Bits); HackTricks.
Files in this version
- SKILL.md2.3 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | c170c1f6 | Signed | – |
More from NoorQureshi
All from this publisherMore in Linux, cloud and containers
See the category- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login