5.2K ·GitHub
What is this?
Exploitarium is a single consolidated archive of the author's public proof-of-concept exploits and vulnerability research writeups, merging dozens of their former standalone PoC repos into one place.
Exploitarium is a single consolidated archive of the author's public proof-of-concept exploits and vulnerability research writeups, merging dozens of their former standalone PoC repos into one place.Is this a runnable tool, or just a collection of writeups?It's a collection, not a single app: most top-level folders are former standalone PoC repos preserved with their original README and files, plus some brand-new self-contained research entries.
It's a collection, not a single app: most top-level folders are former standalone PoC repos preserved with their original README and files, plus some brand-new self-contained research entries.How is the archive organized?Each vulnerability gets its own named folder (e.g., 'objdump-dlx-calc-poc', 'rustdesk-session-permission-pocs'), listed in a Contents table that shows the source repo and number of tracked entries for each.
Each vulnerability gets its own named folder (e.g., 'objdump-dlx-calc-poc', 'rustdesk-session-permission-pocs'), listed in a Contents table that shows the source repo and number of tracked entries for each.Will these PoCs just work against my target as-is?Not necessarily — the author notes that many 'security researchers' struggle to adapt the PoCs to their own environment and plans to broaden the exploits for those cases.
Not necessarily — the author notes that many 'security researchers' struggle to adapt the PoCs to their own environment and plans to broaden the exploits for those cases.Who is this repo meant for?Security researchers and people curious about real exploit development, framed explicitly as open, good-faith vulnerability disclosure meant to draw more people into the field rather than enable attacks.
Security researchers and people curious about real exploit development, framed explicitly as open, good-faith vulnerability disclosure meant to draw more people into the field rather than enable attacks.Have any of these vulnerabilities already been assigned a CVE?At the time each PoC was posted, none had been reported; the author explicitly invites others to report them and take the CVE credit themselves.
At the time each PoC was posted, none had been reported; the author explicitly invites others to report them and take the CVE credit themselves.Did the author use AI to write the actual exploit code?No, the PoCs themselves were hand-typed; the one exception is RustDesk, where AI helped because the author wasn't fluent in that language. Only the READMEs were fully AI-generated and then reviewed for accuracy.
No, the PoCs themselves were hand-typed; the one exception is RustDesk, where AI helped because the author wasn't fluent in that language. Only the READMEs were fully AI-generated and then reviewed for accuracy.How did the author merge their old standalone PoC repos into this one without losing data?Each former repo's Git tree was diffed against its new folder here on path, object type, file mode, and blob ID before the old repos were removed; the check covered 12 repos and 96 tracked entries with zero mismatches.
Each former repo's Git tree was diffed against its new folder here on path, object type, file mode, and blob ID before the old repos were removed; the check covered 12 repos and 96 tracked entries with zero mismatches.Is it okay to actually use these exploits against live systems?No — the README explicitly warns never to use any material in the repo maliciously, positioning this purely as good-faith, open vulnerability disclosure research.
No — the README explicitly warns never to use any material in the repo maliciously, positioning this purely as good-faith, open vulnerability disclosure research.What are similar projects?Claude-Red, h4cker, dirtyfrag, hacker-roadmap, copy-fail-CVE-2026-31431, Relapse-Exploit, bug-bounty-hunting-prompts, CVE-2026-62911
Claude-Red, h4cker, dirtyfrag, hacker-roadmap, copy-fail-CVE-2026-31431, Relapse-Exploit, bug-bounty-hunting-prompts, CVE-2026-62911Which topics is it in?cve, exploit-development, fuzzing, ethical-hacking, ctf, security-research, infosec, vulnerability, exploit, offensive-security, red-team, collection
cve, exploit-development, fuzzing, ethical-hacking, ctf, security-research, infosec, vulnerability, exploit, offensive-security, red-team, collection