# Zero Day Playbook > Runbooks for the first 72 hours after a critical disclosure, by role and asset type, plus the Disclosure Clock of 37 headline bugs from 2026. Zero Day Playbook is a reference that lists and does not rank: vendors are alphabetical, dated records are by date, and every fact has a label, a source link and the date it was read. Every page has a markdown twin at the same address plus index.md (or send Accept: text/markdown). Every fact carries its source and the date it was read (19 Nov 2026). Datasets: https://zerodayplaybook.com/datasets/ (CSV and JSON, CC BY 4.0). ## Home - [Zero day playbook: a 72-hour checklist for your role and the asset that was hit](https://zerodayplaybook.com/index.md): A 72-hour checklist by role and asset for a critical disclosure, plus the Disclosure Clock: 33 of 37 bugs from 2026 have dated exploitation, median 2 days. ## Guide - [Zero day response plan: the complete template with owners, triggers and a drill](https://zerodayplaybook.com/guides/zero-day-response-plan/index.md): A zero day response plan has 10 clauses: scope, triggers, roles, standing approvals, inputs, deadlines, communications, exceptions, records and a drill. - [What to do when a zero day is disclosed: the first four hours, worked on PHP2Shell](https://zerodayplaybook.com/guides/what-to-do-when-a-zero-day-is-disclosed/index.md): In the first four hours after a zero day disclosure, extract seven facts from the advisory, check exploitation signals beyond the CISA catalog. - [Out-of-band patch: how to run one without breaking production](https://zerodayplaybook.com/guides/out-of-band-patch/index.md): An out-of-band patch is a fix applied outside the maintenance calendar because exploitation will not wait. Steps, owners, records and sources, read 19 Nov 2026. - [The board brief by noon: template, interim note and a filled brief for Cisco ISE](https://zerodayplaybook.com/guides/board-brief-by-noon/index.md): Five lines fill the board brief: what is affected, whether exploitation is confirmed, what is done, what is open, and when the next update comes. - [Zero day vulnerability defined: the sources, the tests and six 2026 cases](https://zerodayplaybook.com/guides/zero-day-vulnerability-defined/index.md): Google's threat intelligence group defines a zero-day as a vulnerability "maliciously exploited in the wild before a patch was made publicly available." - [Mitigations that buy time before the patch](https://zerodayplaybook.com/guides/mitigations-that-buy-time/index.md): Mitigations that buy time fall into a few types: restrict the interface, disable the feature, filter at a proxy or WAF, take the service off the internet. - [How to tell where a new CVE hits you](https://zerodayplaybook.com/guides/where-a-new-cve-hits-you/index.md): To tell where a new CVE hits you, check three things in order: the version of every copy of the product, the configuration the advisory requires. - [The 72-hour post-incident review: template and a worked review of the BeyondTrust zero-day](https://zerodayplaybook.com/guides/72-hour-post-incident-review/index.md): Held on day three or four, the review takes 90 minutes, one facilitator who held no role, and a record of eight timestamps. With sources, read 19 Nov 2026. - [Compromise assessment after patching a critical flaw](https://zerodayplaybook.com/guides/compromise-assessment-after-patching/index.md): A patch closes the flaw, not what came through it. A worked hunt for JFrog Artifactory CVE-2026-82329: the window, the requests, admin users, plugins and keys. ## Directory - [Glossary](https://zerodayplaybook.com/glossary/index.md): Twenty zero-day response terms defined in words quoted from NIST, CISA, FIRST, MITRE or OASIS, each with a dated 2026 example and its source. ## About - [About](https://zerodayplaybook.com/about/index.md): Zero Day Playbook is a reference for the first 72 hours after a critical disclosure: 18 playbooks, a checklist and a Disclosure Clock of 37 bugs. - [Editorial policy](https://zerodayplaybook.com/editorial-policy/index.md): How Zero Day Playbook takes sources, sets Clock dates, labels vendor claims and orders its lists, and what it never publishes. Updated 19 Nov 2026. - [Contact](https://zerodayplaybook.com/contact/index.md): Email editor@zerodayplaybook.com with a correction, an earlier exploitation report, a news tip or a data request. Replies within three working days. - [Privacy](https://zerodayplaybook.com/privacy/index.md): Zero Day Playbook sets no cookies and runs no analytics or third-party scripts. The only visit record is the CloudFront access log, deleted after 400 days. - [Terms](https://zerodayplaybook.com/terms/index.md): The Disclosure Clock data is reusable under CC BY 4.0 with its cite line. The site gives general information, not advice. Updated 19 Nov 2026. ## Clock - [The Disclosure Clock: median 2 days to exploitation](https://zerodayplaybook.com/clock/index.md): The Disclosure Clock lists 37 headline bugs of 2026: 33 with a dated exploitation, 12 on or before disclosure day, median 2 days. CSV and JSON downloads. ## Playbook - [The communications playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/communications/index.md): A holding statement, customer update and support script that say only what the incident record supports, with the SEC, NIS2 and GDPR clocks and a worked case. - [The executive playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/executive/index.md): The executive makes four calls in 72 hours: who decides, emergency change authority, downtime, and each risk acceptance. With sources, read 19 Nov 2026. - [The endpoint fleet playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/endpoint-fleet/index.md): Chrome 153.0.8010.36 fixed the exploited V8 flaw CVE-2026-87491 on 8 Sep 2026, yet a browser runs the old code until it relaunches. With conditions and sources. - [Dependency playbook: the first 72 hours when a library you ship has a critical flaw](https://zerodayplaybook.com/playbooks/dependency/index.md): When a library or runtime your application depends on gets a critical flaw, the owning team has 72 hours to find every copy, prove which paths reach it. - [The network edge appliance playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/network-edge-appliance/index.md): Firewalls, VPN gateways and other internet-facing appliances sit in the traffic path. Conditions, fixed builds, timeline and checks, each with its source. - [Cisco ISE network access control playbook: the first 72 hours after a critical flaw](https://zerodayplaybook.com/playbooks/network-access-control/index.md): Cisco Identity Services Engine (ISE) decides which users and devices join wired, wireless and VPN networks. Conditions, fixed builds and checks, with sources. - [Container base image playbook: the first 72 hours when a flaw is in the image your services build on](https://zerodayplaybook.com/playbooks/container-base-image/index.md): A flaw in a container base image sits in every image built on it and in none of your repositories. Conditions, fixed builds, timeline and checks, with sources. - [SaaS vendor playbook: the first 72 hours when the flaw is in a service you cannot patch](https://zerodayplaybook.com/playbooks/saas-vendor/index.md): When the flaw sits in a hosted product, nothing is yours to patch, so the work is proving whether your tenant was hit. With sources, read 19 Nov 2026. - [Email gateway playbook: the first 72 hours after a critical flaw](https://zerodayplaybook.com/playbooks/email-gateway/index.md): A mail gateway reads every message and faces the internet, so a flaw in it exposes mail content as well as the box. Each fact carries its source and read date. - [The remote support tool playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/remote-support-tool/index.md): Remote support tools hold trusted access to many endpoints. ScreenConnect CVE-2026-84869: client versions, the file-transfer role, audit-log hunts and resets. - [The artifact repository and CI system playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/artifact-repository/index.md): An artifact repository holds every build you ship and the tokens that publish them, and the CI system beside it holds the credentials to reach it. - [CMS and storefront playbook: the first 72 hours after a critical flaw](https://zerodayplaybook.com/playbooks/cms-and-storefront/index.md): Content and commerce platforms run public PHP code with writable folders, so one flaw gives a web shell and often payment data. With sources, read 19 Nov 2026. - [The Windows operating system playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/windows-endpoint-os/index.md): Three Windows privilege flaws were exploited when Microsoft shipped their fixes: CVE-2026-68820 on 11 Aug 2026, CVE-2026-85880 and CVE-2026-81963 on 8 Sep 2026. - [The Linux server and SSH playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/linux-server-ssh/index.md): OpenSSH 10.6p2, released 5 Nov 2026 for CVE-2026-123158, closes a password bypass that needs six conditions at once. Each fact carries its source and read date. - [The AI infrastructure playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/ai-infrastructure/index.md): LiteLLM, Langflow and MLflow servers are often started by one engineer, left open, and loaded with model-provider keys and cloud roles. Sourced and dated. - [The developer collaboration platform playbook for the first 72 hours](https://zerodayplaybook.com/playbooks/developer-collaboration-platform/index.md): Self-managed Atlassian products hold source code, tickets and build plans. Conditions, fixed builds, timeline and checks, each with its source. - [Application runtime playbook: the first 72 hours when a flaw is in PHP or another language runtime on your servers](https://zerodayplaybook.com/playbooks/application-runtime/index.md): A flaw in the language runtime that serves your web requests is patched on the host: the package, the server module or pool, and its configuration.