
Redefining vulnerability disclosure in the AI era. We mass-produce exploitable 0days and disclose them directly, using event-driven pressure to elevate vendor security standards and advance the field.
0day vulnerabilities have become rubbish in the AI era.
π Official Website: https://0day-rubbish.com/blog
Traditional vulnerability disclosure is broken. It's slow, bureaucratic, and ineffective. In the AI era, we can mass-produce 0days at scaleβmaking individual vulnerabilities less valuable but more impactful when disclosed directly.
We believe event-driven security hardening is the most effective approach: only when vendors face real, exploitable threats do they prioritize fixes.
Our automated AI systems continuously scan for vulnerabilities across real-world software, identifying potential 0-days through pattern analysis, fuzzing, and intelligent code review.
Each finding undergoes manual validation. We develop working proof-of-concept exploits to confirm exploitability and assess real-world impact.
Every week β Monday or Tuesday β we disclose a new batch of verified, exploitable 0-day vulnerabilities we've discovered and validated:
No delays. No bureaucracy. Just facts.
To all vendors: We hope you can complete fixes before hackers exploit these vulnerabilities.
We partner with:
Our automated vulnerability discovery leverages cutting-edge large language models from leading AI providers:
An AI-driven research process (multi-LLM ensemble: Claude, OpenAI, DeepSeek, GLM, Kimi) discovers 0-days in real-world enterprise software. Every advisory below ships a full root-cause analysis plus a working, reproducible exploit script β no detection-only writeups, no withheld details.
Eleven findings that share one shape: a field an administrator is entitled to type, handed to a shell, a filesystem or a JDBC parser that was never told the field was untrusted. It is the oldest mistake in appliance engineering, and this batch is what it looks like when it is repeated across eleven vendors that each believe their management plane is a trusted environment. Two are reachable with no session at all β a session check that is simply absent from one handler, and an installer that will fetch and unpack an archive from any URL before the product is installed. The other nine sit behind an admin session, and that is exactly why they matter: the credential is the last line, not a mitigation.