Skip to content
Zero Day Playbook

How Zero Day Playbook is written

Sources. Dated claims come from primary pages: vendor advisories and release notes, the CISA directive BOD 26-04 and Known Exploited Vulnerabilities catalog, NVD records, and NIST SP 800-40 Rev. 4 and SP 800-61 Rev. 3. Each is linked with the date it was opened. Quotations are exact and short, and each names its author. A named security firm is used for an exploitation date when it reported first.

Clock dates. Disclosure is the date on the vendor advisory, or the NVD published date when the vendor states none. First exploitation is the earliest dated public report from the vendor or a named security firm. With no such report it is the date of exploitation marked active in CISA's SSVC data in the NVD record, when that data is present. With neither it is the date CISA added the bug to its catalog, which is an upper bound on the first exploitation date, because exploitation can start before CISA lists a bug. In the edition of 19 Nov 2026, 16 rows have a first exploitation date equal to the catalog date and 17 rest on a report dated before the catalog date, 12 from a vendor or named security firm and 5 from CISA SSVC data in NVD records; the source column of the CSV names the page for each. A negative number means exploitation was reported before disclosure, and a bug with no dated exploitation gets no row. Four of the 37 headline bugs have none on 19 Nov 2026: the fastjson 1.x flaw CVE-2026-16723 (disclosed 21 Jul), the Next.js flaw CVE-2026-75604 (25 Aug), the Linux kernel net/unix flaw CVE-2026-80521 (26 Aug) and the Satori and Next.js flaw CVE-2026-94545 (30 Sep). A blank date does not show that a bug is unexploited.

Labels. A fact a vendor states about itself is labeled the vendor's claim, and its words are quoted. A fact from anyone else is labeled a third-party source. Where a page says nothing on a point, the entry reads none found with the read date; that describes the pages read, not the world.

Order. The Clock sorts by measured days, ties by disclosure date. The playbook list on the home page puts the two role playbooks first, then the eleven asset types, in the order the page shows rather than A to Z. The glossary runs A to Z. No page carries a rating, a weight or a position number for any vendor or bug.

Read dates. Every source link carries the date it was read. The playbooks are re-read against the guidance they cite at least every 90 days, and the Clock gains a row once a first exploitation date is published. The Clock and its CVE records were re-read on 19 Nov 2026 against NVD, the CISA feed and vendor advisories.

Never published. The site publishes no exploit code, no proof-of-concept steps and no scanning instructions. Text stays defensive and gives preconditions, detection, mitigation and fix only. It publishes no rating of a vendor and no date it could not source.

Changes. A Clock date moves only when an earlier public report appears. A reader who finds a source that no longer says what a page says can send the address, and the page is checked and changed in the open.

Sources

  1. CISA Known Exploited Vulnerabilities catalog, read 19 Nov 2026
  2. CISA BOD 26-04, Prioritizing Security Updates Based on Risk, read 19 Nov 2026
  3. NIST SP 800-40 Rev. 4, read 19 Nov 2026
  4. NIST SP 800-61 Rev. 3, read 19 Nov 2026

Last reviewed 19 Nov 2026.