Wiki / Zero-Days

Zero-day, n-day, vulnerability and exploit – definitions

Type
Read-up
Steward
Cypher
Facts as of
2026-10-18
Next review
2027-10-18
Status
draft

Zero-day, n-day, vulnerability and exploit – definitions

In one sentence: “zero-day” refers to a vulnerability, or an attack using one, at a point when the party responsible for fixing it has had zero days to release a fix. Authoritative sources define the exact boundary differently.123

The terms

TermDefinitionSource
VulnerabilityA weakness in hardware, firmware or software that an attacker can use.1
ExploitCode or a technique that takes advantage of a vulnerability. CISA defines a proof of concept (PoC) as “the code for a vulnerability that, when executed, would allow for exploitation”.4
Zero-day attack (NIST/CNSS)“An attack that exploits a previously unknown hardware, firmware, or software vulnerability.”1
Zero-day vulnerability (RAND)A software vulnerability “for which no patch or fix has been publicly released”.2
Zero-day (GTIG, in-the-wild counts)“A vulnerability that was maliciously exploited in the wild before a patch was made publicly available.”3
N-day“A vulnerability exploited after its patch has been released.”3
Actively exploited (CISA KEV)Reliable evidence that malicious code was executed on a system without the owner’s permission. Scanning, security research and PoCs do not count.4

Why the differences matter

  • Different definitions give different counts. “Previously unknown” (NIST) and “no public patch” (RAND) cover vulnerabilities that were never exploited. GTIG counts only those exploited before a patch existed.123 Statistics are therefore not comparable across sources unless they use the same definition.
  • States between “known” and “unknown”. RAND calls the alive/dead split “too simplistic” and describes three further states:2
    • living: publicly unknown and actively sought by defenders;
    • immortal: will stay in a product for good because it is no longer maintained;
    • zombie: exploitable in older versions but not in the latest one.
  • Exploitable is not the same as exploited. CISA notes that a public PoC “does not automatically indicate the vulnerability has been or will be exploited”.4

Key facts

  • Average life expectancy of the zero-day vulnerabilities in RAND’s dataset: 6.9 years. 25% did not survive 1.51 years, and 25% lived longer than 9.5 years.2
  • Median time from finding an exploitable vulnerability to a working exploit: 22 days (RAND dataset).2
  • Zero-days exploited in the wild, as counted by GTIG: 75 (2024).3

See also

Changelog

  • 2026-10-18 – created (draft). Open: add a primary-source definition of “vulnerability” (e.g. NIST glossary entry) to replace the paraphrase in row 1.

Sources

  1. NIST CSRC Glossary, “zero-day attack” (sources: CNSSI 4009-2022; NISTIR 8011 Vol. 3). https://csrc.nist.gov/glossary/term/zero_day_attack (accessed 2026-10-18) ↩ ↩2 ↩3 ↩4

  2. L. Ablon, A. Bogart, “Zero Days, Thousands of Nights: The Life and Times of Zero-Day Vulnerabilities and Their Exploits”, RAND Corporation, RR-1751-RC, 2017. https://www.rand.org/pubs/research_reports/RR1751.html (accessed 2026-10-18) ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  3. Google Threat Intelligence Group, “Hello 0-Days, My Old Friend: A 2024 Zero-Day Exploitation Analysis”, 2025-04-29. https://cloud.google.com/blog/topics/threat-intelligence/2024-zero-day-trends (accessed 2026-10-18) ↩ ↩2 ↩3 ↩4 ↩5

  4. CISA, “Known Exploited Vulnerabilities Catalog” – criteria page. https://www.cisa.gov/known-exploited-vulnerabilities (accessed 2026-10-18) ↩ ↩2 ↩3

Cite as: qbZero Wiki, “Zero-day, n-day, vulnerability and exploit – definitions”, as of 2026-10-18. https://qbzero.com/wiki/zero-days/what-is-a-zero-day/