Analysis updated 2026-05-18
Practice exploiting real Kubernetes misconfigurations like privileged pods and over-broad RBAC roles.
Learn how to fix each vulnerability and verify the fix with an automated checker.
Study for a cloud security or Kubernetes security role with hands-on labs instead of slides.
Run a local, disposable CTF environment for team security training.
| hac01/owasp-top-10-k8s-2025 | 0xbennie/binance-smart-money-tracker | aeneasr/dockerstats | |
|---|---|---|---|
| Stars | 44 | 44 | 44 |
| Language | TypeScript | TypeScript | TypeScript |
| Last pushed | — | — | 2021-04-07 |
| Maintenance | — | — | Dormant |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 4/5 | 3/5 | 3/5 |
| Audience | ops devops | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires Docker, kind, kubectl, and Go installed locally, one setup script then builds the cluster and web app automatically.
This project is a hands-on capture-the-flag training environment built around the OWASP Kubernetes Top 10 for 2025, a published list of the most common security weaknesses in Kubernetes clusters. Instead of teaching those risks through slides, it gives you a real, deliberately vulnerable Kubernetes cluster tied to a fictional e-commerce company called NimbusMart, and ten challenges plus one bonus challenge, one for each risk on the list. For each challenge, you get a short mission briefing describing the scenario, a flag you can only reach by actually performing the exploit, such as breaking out of a container or reaching another namespace over the network, and a scoreboard in the web app that tracks your progress. Once you capture a flag, the project also gives you a deep dive on why the weakness exists, a defense guide with concrete fixes, and an automated Go program that checks whether your fix actually closes the hole. Topics covered include privileged containers and node breakout, overly broad permissions in Kubernetes role-based access control, hardcoded secrets, missing network segmentation, exposed internal dashboards, weak authentication, poor logging, and a bonus challenge on using untrusted container images in production. Everything runs locally inside a kind cluster, which is a way of running Kubernetes inside Docker on your own machine, and the README is explicit that the vulnerable setups should never be pointed at a real cluster. A single setup script builds the cluster, a Next.js and React web app, and an in-browser terminal that has full administrative access to that local, disposable cluster only. Getting started requires Docker, kind, kubectl, and Go installed locally, with Node.js needed only if you want to run the web app outside the cluster. This project is aimed at people learning Kubernetes security through practice, such as security engineers, DevOps engineers, or students studying for cloud security roles.
A hands-on capture-the-flag lab where you exploit and then fix ten real Kubernetes security weaknesses in a local, disposable cluster.
Mainly TypeScript. The stack also includes TypeScript, Go, Kubernetes.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.