Exploitation · data as of 16 Nov 2026
From publication to public exploit to attack
When CVEs get a public exploit, when they are seen exploited in the wild, and which come first. 'Exploited' means listed by CISA KEV, ENISA's EUVD, VulnCheck KEV or Google Project Zero; nothing else.
- Exploited CVEs since Nov 2021
- 914
- Median days to first listing
- 7
- Exploited by publication day
- 30%
- Exploited without any public exploit
- 39%
The funnel
# From published to exploited
Of 243 415 CVEs published since November 2021, 3.8% have a public exploit or proof of concept and 0.40% are known to be exploited in the wild.
Bar lengths on a logarithmic scale.
Timing
CVEs published since 3 November 2021, when CISA’s list started; older CVEs were added to it in bulk, which would distort the timing.
# Days from publication to first 'exploited' listing
Half of the 914 exploited CVEs published since November 2021 were listed within 7 days. 30% were already being exploited when published (zero-days), 51% within a week.
- Before publication
- Same day
- After
# Days from publication to first public exploit
For 8 729 CVEs published since November 2021 with a public exploit, the median wait was 5 days; 27% had one before the CVE was published.
- Before publication
- Same day
- After
# Did a public exploit come first?
Of 916 exploited CVEs (published since November 2021), 39% never had a public exploit: attackers did not need one.
# Median days to first exploited listing, by publication year
Recent years look faster partly because slow cases have not happened yet.
Zero-days
# Exploited CVEs per year, zero-day or not
By year of first listing; CVEs published since November 2021.
- Exploited on or before publication
- Exploited after publication
# Project Zero: zero-days caught in the wild
Google Project Zero's tracker. Where it records both dates, the median time from discovery to patch was 9 days (132 cases).
# Whose software the in-the-wild zero-days hit
Vendors in Project Zero's in-the-wild list, all years.
# CISA KEV additions per year, by ransomware use
CISA marks KEV entries known to be used in ransomware campaigns.
- Known ransomware use
- No known ransomware use
The lists
# Who says it is exploited
CISA lists 1 781 CVEs, ENISA 1 798. ENISA's list includes 1 781 of CISA's and adds 17 of its own; 0 are on CISA's list only.
Proof-of-concept hype
# Most claimed proofs of concept on GitHub
CVEs with ten or more PoC repositories are exploited in 51% of cases; with one to nine, 6%. Many repositories are fakes or scanners.
| CVE-2026-109618 | 778 | Yes | 100% | RCE via OOM corruption |
| CVE-2021-44228 | 509 | Yes | 100% | Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints |
| CVE-2025-55182 | 459 | Yes | 100% | – |
| CVE-2026-31431 | 324 | Yes | 98% | crypto: algif_aead - Revert to operating out-of-place |
| CVE-2026-43499 | 194 | no | 5.4% | rtmutex: Use waiter::task instead of current in remove_waiter() |
| CVE-2021-4034 | 184 | Yes | 95% | – |
| CVE-2021-41773 | 176 | Yes | 100% | Path traversal and file disclosure vulnerability in Apache HTTP Server 2.4.49 |
| CVE-2025-29927 | 134 | no | 99% | Authorization Bypass in Next.js Middleware |
| CVE-2019-0708 | 122 | Yes | 100% | – |
| CVE-2022-0847 | 110 | Yes | 93% | – |
| CVE-2022-22965 | 100 | Yes | 100% | – |
| CVE-2024-6387 | 97 | no | 100% | Openssh: regresshion - race condition in ssh allows rce/dos |
| CVE-2014-6271 | 96 | Yes | 100% | – |
| CVE-2022-30190 | 95 | Yes | 98% | Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution Vulnerability |
| CVE-2026-111497 | 93 | Yes | 83% | Out-of-Bounds Write in Google Brotli Decoder |