Skip to content

About

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.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Β 
Β 

Latest commit

Β 

History

18 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

0day Rubbish

0day vulnerabilities have become rubbish in the AI era.

License: MIT Latest batch Max CVSS PoC Website Watchers Discussions Last commit

🌐 Official Website: https://0day-rubbish.com/blog


🎯 Why This Exists

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 Disclosure Process

Step 1: AI Discovery

Our automated AI systems continuously scan for vulnerabilities across real-world software, identifying potential 0-days through pattern analysis, fuzzing, and intelligent code review.

Step 2: Verification & PoC Development

Each finding undergoes manual validation. We develop working proof-of-concept exploits to confirm exploitability and assess real-world impact.

Step 3: Periodic Public Disclosure

Roughly every two weeks we disclose a new batch of verified, exploitable 0-day vulnerabilities we've discovered and validated:

  • Full technical analysis and root cause
  • Working PoC exploit code
  • Affected versions and systems
  • Impact assessment
  • Recommended mitigations

No delays. No bureaucracy. Just facts.

To all vendors: We hope you can complete fixes before hackers exploit these vulnerabilities.

⚑ Core Principles

  • Real-world impact only: We disclose only vulnerabilities that affect real-world systems with actual user bases
  • No worthless targets: Non-exploitable vulnerabilities or devices with negligible user adoption are excludedβ€”they're rubbish with zero value
  • Speed over protocol: Direct disclosure drives faster action than traditional channels
  • Proof over claims: Every disclosure includes working exploits
  • Impact over quantity: Focus on high-severity, widely-deployed vulnerabilities
  • Transparency: Full technical details, no hidden agendas
  • Non-profit: Driven by passion for security research, not financial gain

🀝 Collaboration

We partner with:

  • Top AI model providers advancing automated security research
  • Security researchers exploring AI-powered discovery

πŸ€– AI Models Used

Our automated vulnerability discovery leverages cutting-edge large language models from leading AI providers:

  • Anthropic (Claude) - Deep security pattern recognition and reasoning
  • OpenAI - Advanced reasoning and code analysis
  • DeepSeek - Specialized vulnerability detection
  • Z.ai (GLM) - Long-context code analysis
  • Moonshot (Kimi) - Long-context security analysis

πŸ“‹ Disclosed Vulnerabilities

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.

Latest Batch β€” Batch 6 (7 advisories)

# Product Affected Version CVSS Class Advisory & PoC
1 JetBrains Datalore On-Premises 2026.2.3 9.8 Unauth RCE via InteractiveReport access-mapping flaw InteractiveReport READ→EXECUTE → Unauth RCE
2 Docmosis Tornado 2.11.3 9.8 Unauth Arbitrary File Write β†’ cron (Root) storeTo=file: β†’ Root RCE
3 ActFax 10.70 9.8 Unauth LPD Ghostscript %pipe% (SYSTEM) LPD %pipe% β†’ SYSTEM RCE
4 RoboTask 11.0.5.1229 9.8 Unauth REST API Task Execution REST API Unauth β†’ Task RCE
5 Countersoft Gemini 7.3.0 8.8 Auth SQLi β†’ xp_cmdshell (SYSTEM-able) SQLi β†’ xp_cmdshell RCE
6 Veeam ONE Reporter 13.1 8.8 Auth Command Injection β†’ Local Admin CommandExecutor β†’ Local Admin RCE
7 Wavestore VMS 6.48.809 8.8 Auth Cmd Injection β†’ Root venusd /simple/export β†’ Root RCE

Totals: 7 advisories Β· 7 vendors Β· 4 unauthenticated Β· 3 authenticated (deep-chain) Β· 6 root/SYSTEM Β· all with reproducible PoC.

Earlier batches: Batch #1 Β· Batch #2 Β· Batch #3 Β· Batch #4 Β· Batch #5


πŸ” An Ongoing Series β€” Weekly Disclosures

This is a continuous disclosure series. Thanks to continuous optimization, the AI-driven discovery pipeline now produces new 0-day findings at a stable daily rate, and we disclose verified batches on a weekly cadence.

  • Latest batch: Batch 6 β€” 7 advisories (live); cumulative 58 across 6 batches
  • Next drop: weekly
  • Future scope: expanding beyond enterprise IT into ICS / SCADA, energy, and aerospace systems

If you want to catch the next drop the moment it lands:

Star Watch Blog

⭐ Star to bookmark Β· πŸ‘ Watch (custom β†’ Releases + Discussions) for new batches Β· 🌐 Follow the blog for per-advisory updates.


πŸ“‚ Vulnerability Submission Format

All disclosed vulnerabilities follow a standardized directory structure:

product/
└── <vendor>/
    └── <version>/
        └── <vulnerability_type>/
            β”œβ”€β”€ exploit/          # Exploit scripts and PoC code
            β”œβ”€β”€ analysis.md       # Detailed vulnerability analysis
            └── summary.md        # Brief vulnerability overview

Directory Rules

  • product/: Root directory for all vulnerabilities
  • /: Vendor or product name (e.g., apache, cisco, sonicwall)
  • /: Affected version range (e.g., 6.11.0, 12.4.2)
  • <vulnerability_type>/: Classification (e.g., unauth-rce, auth-bypass, deserialization-rce)

Required Files in Each Vulnerability Directory

  1. exploit/: Directory containing working exploit scripts and PoC code
  2. analysis.md: Comprehensive technical analysis including root cause, attack vector, and impact
  3. summary.md: Concise vulnerability overview with affected versions and quick mitigation steps

Example

product/
└── sonicwall/
    └── sma-12.4/
        └── preauth-deserialization-rce/
            β”œβ”€β”€ exploit/
            β”‚   └── poc.py
            β”œβ”€β”€ analysis.md
            └── summary.md

Join us in redefining vulnerability disclosure for the AI era.

About

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.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages