Someone dumped 23 zero-day exploits on GitHub with zero vendor warning

An anonymous GitHub account called “bikini” published a repository named “exploitarium” on June 23, packing proof-of-concept exploits for 23 previously unreported vulnerabilities across some of the most widely used open-source software on the planet. libssh2, FFmpeg, Ghidra, nmap, Docker, VLC, OpenVPN, PHP, Gitea, Firefox, c-ares, AnyDesk, RustDesk. By June 27, the repo had 1.7k stars, 360 forks, and 46 commits. By June 28, it was still growing.

The README is blunt. “At the time I post these, none have been reported. Feel free to report them yourself and take credit for the CVE if handed out lulz.” The author claims this is good-faith open disclosure meant to attract people to the security field. No vendor was contacted first. No coordinated disclosure window. The exploits went straight to public GitHub.

The repo description reads like a dare. The profile bio says “All I do is spam unpatched vulnerabilities I discover after responsibly disclosing them (sometimes) and update patchwork.” The parenthetical is doing a lot of work there.

What got hit

The most serious finding is CVE-2026-58053, a vulnerability in Gitea’s act_runner with Docker backend. The runner passes a workflow’s container.options string unsanitized. CVSS 9.9 out of 10. Critical. Anyone running Gitea CI with Docker runners is exposed.

CVE-2026-55200 hits libssh2 with an out-of-bounds write in ssh2_transport_read(). The function fails to enforce upper bounds on packet_length. A crafted SSH packet corrupts heap memory and achieves remote code execution. Affects libssh2 through 1.11.1. This one is real and serious. libssh2 maintainers already merged fixes (commits 97acf3df and 1762685).

Additional CVEs already assigned: CVE-2026-58050 and CVE-2026-58051 (libssh2 publickey list issues), CVE-2026-58054 (MyBB privilege escalation), CVE-2026-58055 (nghttp2 proxy queue poisoning). GitHub Advisory Database has published advisories for all of them, each referencing the exploitarium PoC paths directly.

Other targets in the dump include a c-ares TCP use-after-free, a Docker cp copyout destination escape, a Firefox SmartWindow private URL exfiltration bug, an FFmpeg RASC DLTA calculation vulnerability, an nmap IPv6 extension length wrap, a PHP streambucket SOAP RCE, and a VLC VP9 crash. The full list spans 23 exploit directories.

Not all of these are real

The HN thread (858 points, 331 comments) picked the repo apart. The Ghidra exploits got demolished. Retr0id, the top commenter, pointed out that the first Ghidra PoC requires overwriting binaries in the Swift tool directory. “Yes, if you overwrite binaries executed by ghidra, you can trigger code execution. This is not a surprise.” The third Ghidra finding was called “not a vulnerability in the slightest.”

But the serious ones held up. newguy33 confirmed the c-ares, libssh2, and FFmpeg PoCs “all work as of the latest upstream commit.” The nmap IPv6 bug drew particular concern. athrowaway3z noted “there’d be a certain irony being able to reverse shell anyone doing an nmap scan.”

The split is roughly: a third are legitimate and serious, a third are technically real but low impact, and a third are noise. That noise ratio matters because defenders cannot tell which third they are in without auditing every PoC themselves.

The AI angle

The author used GPT-5.5-3-Codex-Spark for all the fuzzing, with what they describe as “a strict harness.” They hand-typed the PoCs themselves, except for RustDesk where AI assistance was used. The README files are, in the author’s own words, “very clearly entirely AI” generated.

This is the part that should worry people. An AI-assisted fuzzing pipeline that produces 23 exploit PoCs in a matter of days, with zero vendor coordination, published to a public repo that anyone can clone. The barrier to mass 0-day disclosure just dropped significantly.

Defenders are not happy

On Reddit’s r/hackernews, the top comment captures the frustration: “Watching an anonymous account dump undisclosed 0-days into a public repo with zero coordination is rough on defenders. By the time a vendor sees the writeup, scanners have already weaponized the bug.”

The timing made it worse. The bulk of the dump landed on a Saturday. Security teams at affected vendors were working weekend rotations. libssh2 managed to push fixes within 48 hours. Ghidra (NSA), nmap, Mozilla, Docker, and FFmpeg had not issued formal statements as of June 28.

Some speculated the account is connected to a researcher known as “Nightmare-Eclipse,” who released Windows 0-days (BlueHammer, UnDefend, RoguePlanet) starting April 2026, was banned from GitHub on May 23, and vowed to keep dropping exploits. The bikini author’s targets are open-source tools rather than Windows, and their stated motivation is academic rather than retaliatory. The connection remains unconfirmed.

The author promises more. A recent commit message reads “New drops today ;) Biggest thing yet.” The plan is daily PoC releases going forward. Only “serious” vulnerabilities will be shared from here on, which by their own list includes Floci, libssh2, and FFmpeg.

The GitHub Advisory Database, Debian Security Tracker, and Tenable have already created entries. CVEs are being assigned in real time by whoever files them first. The repo explicitly invites this: “Feel free to report them yourself and take credit for the CVE.”

libssh2 is patched. Gitea needs patching. Everything else is a question mark.