Verified Reproductions
Autonomously reproduced vulnerabilities, bugs, and regressions. Each reproduction gets a permanent REPRO-YYYY-NNNNN identifier.
59
Reproductions
13
Ecosystems
20m 6s
Avg. Duration
100%
Autonomous
Latest Reproductions
View all → REPRO-2026-00130 published
pymetasploit3 command injection
Security critical PyPI
DanMcInerney/pymetasploit3
36m 8s Apr 4, 2026
REPRO-2026-00129 published
Go MCP SDK DNS Rebinding - Server-Side Request Forgery on AI Infrastructure
Security high Go module
github.com/modelcontextprotocol/go-sdk
38m 55s Apr 4, 2026
REPRO-2026-00128 published
Haraka Mail Server DoS via __proto__ prototype pollution in email headers
Security high github
npm/Haraka
17m 5s Apr 4, 2026
REPRO-2026-00127 published
cpp-httplib HTTP Request Smuggling via Unconsumed GET Request Body
Security high github
yhirose/cpp-httplib
61m 29s Apr 4, 2026
REPRO-2026-00126 published
Cesanta Mongoose mDNS Stack Buffer Overflow - Remote Code Execution PoC
Security critical github
cesanta/mongoose
53m 53s Apr 2, 2026
REPRO-2026-00125 published
Grafana SQL Expressions RCE
Security critical github
grafana/grafana
59m 16s Apr 1, 2026
Why REPRO IDs?
Verified Proof
Each reproduction includes executable scripts, session replays, and before/after evidence proving the vulnerability exists.
Permanent Citation
REPRO IDs are permanent, citable references. Link CVEs, GHSAs, and issues to verified reproductions.
Full Transparency
Watch session replays showing exactly how the agent reproduced the issue. Nothing hidden, everything auditable.
Embed in Your README
Show that your security advisory has been independently verified with an embeddable badge.
[](https://pruva.dev/REPRO-2026-00001)