From d589bab5b290b67f893930ec92b50d931b472ef7 Mon Sep 17 00:00:00 2001 From: Amitai Cohen Date: Sun, 18 Oct 2026 11:08:54 +0300 Subject: [PATCH] Raise CVE ID plausibility limits to match 2026 allocation pace The per-month cap (5000/month, i.e. 50k in October) rejects most current 2026 IDs: CVE-2026 IDs above 111k are already published. In hunt run #564, 10,711 of 13,813 RSS mentions were dropped as "implausibly high", and these are the newest IDs, the likeliest ghosts. Raise max_id_per_month to 25000 (~2x the observed 2026 pace) and the 2026 entry in max_id_by_year to 300000, which applies once 2026 is a past year. Co-Authored-By: Claude Opus 5.5 --- src/config.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/config.py b/src/config.py index 6db84d5..571d124 100644 --- a/src/config.py +++ b/src/config.py @@ -50,15 +50,16 @@ class CVEValidationConfig: # Updated limits based on actual CVE allocations (some CNAs have large blocks) max_id_by_year: dict[int, int] = field(default_factory=lambda: { 2025: 100000, # Raised: published CVEs exist above 70k - 2026: 30000, # We're in March 2026, raised to accommodate large CNA blocks + 2026: 300000, # 2026 IDs above 111k were already published by October 2027: 0, # Future year - no CVEs yet 2028: 0, 2029: 0, }) # For current year, maximum plausible ID based on month - # Tightened from 6000 to 5000 to reduce false positives - max_id_per_month: int = 5000 + # 2026 allocation is running at ~11.5k/month; 25k leaves ~2x headroom + # while still rejecting obvious fakes (e.g. 6-digit IDs early in the year) + max_id_per_month: int = 25000 # Suspicious patterns to reject reject_all_zeros: bool = True # CVE-2025-0000000