cdk-team/cdk

📦 Make security testing of K8s, Docker, and Containerd easier.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 14th, 2026
Created on November 5th, 2020
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 608
Total Stargazers: 4,752 (+0)
Total Subscribers: 73 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.9 hours
Mean response time: 47.6 days
90th percentile: 289.5 days
Tracked items: 8

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 717 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (2)
  • Improvement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

CDK is a container penetration toolkit designed for security testing of Kubernetes, Docker, and Containerd environments.

CDK addresses the challenge of performing security assessments within slimmed-down containers that lack standard OS tools and dependencies. It works by bundling exploitation capabilities and diagnostic tools into a single zero-dependency binary that can be deployed directly into a target container. The toolkit operates through three core modules: an Evaluate module that gathers information about the container environment and identifies potential weaknesses, an Exploit module that provides proof-of-concept and working exploits for container escape and lateral movement, and a Tool module offering network utilities and Kubernetes cluster management capabilities. Users run `cdk eva` to assess the environment and receive exploit recommendations, then execute `cdk run` to deploy the chosen attack.

The tool suits penetration testers and security researchers conducting authorized assessments of containerized infrastructure. It is particularly valuable in scenarios where the target container has minimal tooling available, making traditional penetration testing approaches difficult. The Evaluate module covers information gathering across system basics, Linux capabilities, mounts, network namespaces, sensitive environment variables, processes, local files, and Kubernetes API discovery. The Exploit module provides working attacks for container escape and cluster takeover. CDK distinguishes itself by requiring no external dependencies and being deliverable as a single binary, making it practical for real-world penetration testing where file upload or remote code execution may be the only initial access vector.

The project maintains active development with regular updates to exploit modules and evaluation capabilities. The codebase shows consistent refinement of existing features and addition of new exploitation techniques. Documentation is comprehensive, with detailed wiki pages covering each evaluation check and exploit scenario. The project demonstrates responsiveness to the container security landscape through ongoing additions to its exploit library.