Flagged Before They Were Listed as Exploited
Every vulnerability below was flagged by VulNow before it was added to a Known Exploited Vulnerabilities (KEV) catalog. KEV catalogs record exploitation that has already been observed: they are confirmation, not warning.
All 15, by lead time
| CVE | Project | Severity | Lead Time | Notes |
|---|---|---|---|---|
| CVE-2026-40478 | Thymeleaf | Critical | 197 days | Reproduced with a working PoC the day it was flagged |
| CVE-2026-11645 | V8 | High | 39 days | |
| CVE-2026-66066 | Rails | Critical | 27 days | |
| CVE-2026-1207 | Django | High | 23 days | |
| CVE-2026-40466 | ActiveMQ | High | 20 days | |
| CVE-2026-34197 | ActiveMQ | High | 17 days | |
| CVE-2026-126081 | Rails | High | 12 days | |
| CVE-2026-89013 | Dolibarr | High | 11 days | Reproduction scored it High (8.7 CVSS 4.0, 7.5 CVSS 3.1), matching the official score |
| CVE-2026-111497 | Node2Shell | Critical | 5 days | |
| CVE-2026-120203 | ShowDoc | High | 4 days | |
| CVE-2026-48710 | Starlette | Medium | 4 days | 103 days before CISA KEV |
| CVE-2026-119977 | WordPress | High | 2 days | 6 days before CISA KEV |
| CVE-2026-19478 | GitLab | Critical | 2 days | |
| CVE-2026-87902 | WordPress | High | Same day as VulnCheck KEV | 3 days before CISA KEV |
| CVE-2026-3910 | V8 | High | Same day as VulnCheck KEV | 1 day before CISA KEV |
Lead time is how far ahead of the earliest KEV listing VulNow's signal arrived. CISA maintains the best-known KEV catalog; VulnCheck maintains a broader catalog that often lists exploitation earlier. Where a CISA KEV listing came later, the lead before it is shown in the notes. Last updated: Nov 18, 2026.
Two cases in detail
Thymeleaf: a working exploit six months before KEV
The Thymeleaf finding for CVE-2026-40478 (VULNOW-2026-02761) was automatically reproduced with our weaponizer on the exact day it was flagged.
- Mar 27, 2026. Flagged and reproduced with a working PoC.
- Apr 15, 2026. Public advisory published (19 days later).
- Oct 10, 2026. Added to VulnCheck KEV (197 days after reproduction).
That means a verified, working exploit for a Critical (9.0) Thymeleaf vulnerability was already confirmed more than six months before it was catalogued as exploited in the wild.
Dolibarr: severity scored by reproduction
Automated reproduction also scores severity before official advisories are published. For Dolibarr's CVE-2026-89013 (VULNOW-2026-21854), the reproduction rated it High: 8.7 (CVSS 4.0) and 7.5 (CVSS 3.1). That matched the official score, and it was 11 days ahead of the KEV listing.
At scale, detecting, reproducing, and accurately scoring vulnerabilities ahead of advisories and KEV catalogs turns reactive patching into planned remediation, giving engineering teams time before exploitation begins.