explaingit

unclecheng-li/poc-lab

59CAudience · researcherComplexity · 4/5ActiveLicenseSetup · hard

TLDR

Collection of proof of concept scripts and reproduction notes for recently disclosed CVEs across Linux kernel, Windows, macOS, containers, and services.

Mindmap

mindmap
  root((poc-lab))
    Inputs
      CVE identifier
      Affected version
      Target system
    Outputs
      Exploit script
      Reproduction notes
      Patch references
    Use Cases
      Reproduce a CVE in a lab
      Study exploit mechanics
      Verify patches
    Tech Stack
      Python
      Shell
      C

Things people build with this

USE CASE 1

Reproduce a recent kernel or service CVE inside an isolated lab VM

USE CASE 2

Verify whether a patch actually closes a known vulnerability

USE CASE 3

Train red team or blue team staff on real exploit mechanics

Tech stack

PythonShellC

Getting it running

Difficulty · hard Time to first run · 1day+

Each entry needs its own vulnerable target environment (specific kernel, service version, or container) and must only be run against systems you own.

MIT license: free to use, modify, and redistribute with attribution and no warranty.

In plain English

poc-lab is a collection of proof of concept scripts and reproduction steps for recently disclosed software vulnerabilities. The README describes the focus as fresh, high severity CVEs covering the Linux kernel, Windows, macOS, containers, and various services. It is set up as a reference repository for security researchers who want to study how specific bugs work in practice. The layout is the same for every entry. Each vulnerability lives in its own directory, named after the CVE identifier when one exists, or after the vulnerability's public name when no CVE has been assigned. Inside that directory there is an exploit script, either a Python file called exploit.py or a shell file called exploit.sh, and a README that lists the CVE, the affected versions, reproduction steps, and references such as advisories and patch commits. Getting started is described in a short shell snippet. You clone the repository, change into a chosen vulnerability folder, read its README, then run either python3 exploit.py or bash exploit.sh depending on which file is present. There is no central build step or test harness in the top level README. The contributing section invites pull requests that add new vulnerability directories. A new entry should follow the same template: a CVE or name based directory, the exploit script, and a README that includes the CVE identifier, the affected components, a step by step reproduction guide, and links to credits and advisories. The README ends with a clear disclaimer. The author states the repository is for security research and educational use only, asks readers not to use the scripts against systems they do not own or have permission to test, and points to responsible disclosure as the expected practice. A linked sister project called VulnClaw is described as an AI powered penetration testing framework. License is MIT.

Copy-paste prompts

Prompt 1
Pick a Linux kernel CVE folder in poc-lab and walk me through running exploit.py inside a Ubuntu VM
Prompt 2
Build a Dockerfile that boots the affected version of a service from a poc-lab entry so I can reproduce the CVE safely
Prompt 3
Add a new poc-lab directory for CVE-2025-XXXX following the existing template with exploit.sh and a CVE README
Prompt 4
Diff a vulnerable and patched build for one poc-lab entry and explain which lines fix the bug
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.