Sign in (or create an account) to track this CVE across sessions.
CERT-In × CISA KEV
The exploit is live. Is the warning?
When a CVE is confirmed under active attack, how many days pass before India's national CERT tells anyone? This measures that gap across 2026 — vendor by vendor.
📅 Year: 2026🔎 Matched: 123 CVEs🗂 Source: 2026 run
Perimeter
WAF + rate limit
Access control
Auth · JWT
App layer
Least privilege
⚠ Warning lag
+1 day median
Showing the 2026 run. Load your joined.csv to recompute every number from your real data — all local, nothing uploaded.
The finding
How timely were the warnings?
Every exploited CVE, split by when CERT-In warned relative to CISA's confirmed exploitation date.
Before CISA Within 6 days 7+ days late
Median lag by vendor
Isometric bars, longest gap first. Positive = CERT-In warned later than CISA confirmed exploitation.
Matched CVEs
Load joined.csv to list every exploited CVE with both dates and the lag.
CVE
Vendor
CISA exploited
CERT-In warned
Lag
Watch
No rows loaded yet.
Method & honest caveats
How it's measured
Collect every CERT-In Vulnerability Note for the year; extract its publish date and CVE IDs.
Download CISA's Known Exploited Vulnerabilities (KEV) catalog — CVEs confirmed exploited in the wild, with the date each was added.
Match by CVE ID. Lag = CERT-In advisory date − CISA KEV date. Keep CERT-In's first mention of each CVE.
What the numbers actually say
CERT-In is fast on average — median lag near zero, sometimes warning before CISA. The story isn't "India is slow." A minority of cases run a week or more late, concentrated in specific vendors.
The matched set is small (CVEs in both CERT-In notes and CISA KEV). Per-vendor medians rest on a handful of CVEs each — directional, not statistically strong. Running 2023–2024 widens the base.