Skip to content

Raise CVE ID plausibility limits to match 2026 allocation pace #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
korniko98 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Raise CVE ID plausibility limits to match 2026 allocation pace #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions src/config.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down