Low Severity
Published: Oct 27, 2026

[GitHub] cve_collector_public

Other
Type
N/A
CVSS Score
114
Views
Anonymous
Author

Description

# CVE Vulnerability Research Pipeline

Automatically collect PoCs confirmed for actual CVEs daily, and from there **it branches into two paths**.

```
Collect (automatic) ─ Filter (automatic) ─┬─ CTF problem creation material data/study/, data/high-severity.md
└─ Patch analysis → Bypass discovery → Vendor report
data/analysis.json, reports/
```

Both are primary objectives. Collection is a common input stage for both paths, and in fact, 3 out of 5 reports sent so far have come from this archive.

- Data sources: [NVD](https://nvd.nist.gov/), [CISA KEV](https://www.cisa.gov/known-exploited-vulnerabilities-catalog), [GitHub Advisory Database](https://github.com/advisories), [GitHub Repository Search](https://github.com/search)
- Collection cycle: Once daily, `0 3 * * *` UTC (GitHub Actions `.github/workflows/collect.yml`)
- Filter: Only save CVSS ≥ 6.0 with confirmed PoC (regardless of publication date — old CVEs collected if PoC emerges today)
- Format: Markdown file per CVE (`data/<year>/<CVE-ID>.md`)
- Study full list: Keep entire archive items with CVSS ≥ 8.0 always up-to-date in `data/high-severity.md`
- Study daily allocation: Distribute 5 items daily without duplication to `data/study/<CVE-ID>.md`. Today's new promotions → existing archive → scan NVD entire DB in descending CVSS order for items with PoC

> This file is auto-generated/overwritten when `scripts/collect.py` runs. Do not edit directly.

## How It Works

1. Add newly published CVEs from NVD (CVSS ≥ 6.0) to candidate pool (`data/.pool.json`)
1b. Also add previously published CVEs at 5 items daily sorted by CVSS descending (CRITICAL→HIGH→MEDIUM buckets) regardless of publication date; backfill with cursor saved in state file
2. Detect candidates with newly attached Exploit reference tags cheaply via NVD lastModified bulk query
3. For candidates not caught above, recheck at revalidation milestones (3/7/14/30/60/90/180/365 days after publication) via GitHub repository search
4. If PoC confirmed, save to `data/<year>/<CVE-ID>.md` with enriched CISA KEV/GHSA information and remove from pool
5. If PoC not found after completing schedule, discard and remove from pool (does not remain in archive)
6. Regenerate `data/high-severity.md` each time by filtering only CVSS ≥ 8.0 from entire archive
6b. Incrementally query GHSA by updatedSince, ingest **only those with patch commits** into analysis queue (`data/analysis.json`) (do not add to candidate pool — GHSA lacks PoC information)
7. Daily 5-item study allocation → `data/study/<CVE-ID>.md`. Priority 1: today's new promotions, Priority 2: existing archive, Priority 3: scan NVD entire DB in descending CVSS order for items with PoC (regardless of publication date, continue from cursor)

## Local Execution

```bash
pip install -r requirements.txt
cd scripts
python collect.py # Incremental collection (based on state file)
python collect.py --days 3 # Force backfill of recent 3 days' new CVEs
python collect.py --verify # Archive PoC verification
```

Translated to English from Korean. Show original · see the source links.
Community Rating
0

Login to rate this exploit

Quick Actions