The zero-day lifecycle
In one sentence: the zero-day lifecycle is the sequence of stages a software vulnerability passes through, from the moment the flaw exists to the moment users have removed it. It is called a zero-day for the period in which it is exploited before a fix is publicly available.1
Definitions used on this page
- Zero-day (in-the-wild sense): “a vulnerability that was maliciously exploited in the wild before a patch was made publicly available”. This is the definition used by Google Threat Intelligence Group (GTIG) in its annual counts.1 Other sources use the term more broadly for any vulnerability unknown to the vendor; see
what-is-a-zero-day. - N-day: “a vulnerability exploited after its patch has been released”.1
- Coordinated vulnerability disclosure (CVD): “the process of gathering information from vulnerability finders, coordinating the sharing of that information between relevant stakeholders, and disclosing the existence of software vulnerabilities and their mitigations to various stakeholders including the public”.2
The stages
| # | Stage | What happens | Reference |
|---|---|---|---|
| 1 | Introduction | A flaw is created in design or code and shipped in a product. | — |
| 2 | Discovery | Someone finds the flaw: the vendor, an independent researcher, or an attacker. Vendors “have no monopoly on the ability to discover vulnerabilities in their products and services”.2 | 2 |
| 3 | Exploitation before a fix (zero-day period) | If an attacker uses the flaw before a public patch exists, it counts as a zero-day under the in-the-wild definition.1 This stage does not occur for every vulnerability. | 1 |
| 4 | Report to the vendor | The finder reports the flaw, directly or through a coordinator. ISO/IEC 29147 gives vendors requirements and recommendations for receiving reports; ISO/IEC 30111 covers handling them internally.3 | 23 |
| 5 | Remediation | The vendor develops a fix or mitigation. | 3 |
| 6 | Public disclosure | The vendor publishes the fix and an advisory. A CVE ID is assigned by a CVE Numbering Authority, and the record is published with a description and at least one public reference.4 | 34 |
| 7 | N-day period | Exploitation can continue against systems that are not yet updated.1 If there is reliable evidence of exploitation in the wild and a clear remediation, CISA can add the vulnerability to its Known Exploited Vulnerabilities (KEV) catalogue.4 | 14 |
| 8 | Remediation by users | Users apply the update, or remove the product if it is end-of-life and cannot be updated.4 | 4 |
The order of stages 3–6 varies. A flaw can be exploited before it is reported, between report and fix, or never.
Why it matters for security
- The zero-day period is the window in which defenders have no vendor fix available. GTIG counted 75 zero-days exploited in the wild in 2024, 98 in 2023 and 63 in 2022.1 GTIG notes that these counts cover only exploitation that was detected and disclosed.1
- The n-day period depends on how fast users update. US federal civilian agencies must remediate KEV-listed vulnerabilities within set deadlines under Binding Operational Directive 22-01. Other organisations are not bound by it, but CISA recommends they do the same.4
- GTIG states that exploitation counts per vendor are “not necessarily reflective of a vendor’s security posture or software development processes”, because targets depend on attackers’ goals.1
Key facts
- Zero-days exploited in the wild: 75 (2024), 98 (2023), 63 (2022), as tracked by GTIG.1 Source type: the party’s own research report.
- Share of 2024 zero-days affecting enterprise technologies: 44% (33 of 75).1 Of those 33, 20 were in security and networking software and appliances: over 60% of enterprise zero-day exploitation.1
- The CERT Coordination Center has coordinated vulnerability disclosures since 1988.2
- ISO/IEC 29147:2018 (vulnerability disclosure) was confirmed in 2024 and is marked “to be revised” (2025-09-26).3
See also
- Zero-day, n-day, vulnerability and exploit: definitions
- Coordinated vulnerability disclosure
- CVE, CVSS and the KEV catalogue
- Harvest now, decrypt later: a case where data captured during one period is exploited in a later one.
Changelog
- 2026-10-18 – created (draft). Open: check whether GTIG has published a 2025 count.
Sources
-
Google Threat Intelligence Group (C. Charrier, J. Sadowski, C. Lecigne, V. Stolyarov), “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 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13
-
CERT Coordination Center, Software Engineering Institute, “The CERT Guide to Coordinated Vulnerability Disclosure” (web edition of CMU/SEI-2017-SR-022). https://certcc.github.io/CERT-Guide-to-CVD/ (accessed 2026-10-18) ↩ ↩2 ↩3 ↩4 ↩5
-
ISO/IEC 29147:2018, “Information technology — Security techniques — Vulnerability disclosure”, catalogue page. https://www.iso.org/standard/72311.html (accessed 2026-10-18) ↩ ↩2 ↩3 ↩4 ↩5
-
CISA, “Known Exploited Vulnerabilities Catalog” – criteria page. https://www.cisa.gov/known-exploited-vulnerabilities (accessed 2026-10-18) ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7