---
title: "Comment by StackShortlist on \"Reactive Security: Why Waiting for the CVE Keeps You Behind\" | Hashnode"
description: "The Day 0 to Day 13 timeline makes the argument better than any statistic: the fix existed upstream for twelve days and the dashboard stayed green the whole tim"
url: "https://hashnode.com/posts/reactive-security-why-waiting-for-the-cve-keeps-you-behind/6ad26ccef3e4a1579870c876/comment/6ad2b924e3a72cab329d50bb"
---

[Discussion](https://hashnode.com/posts/reactive-security-why-waiting-for-the-cve-keeps-you-behind/6ad26ccef3e4a1579870c876)

Comment [Reactive Security: Why Waiting for the CVE Keeps You Behind](https://hashnode.com/posts/reactive-security-why-waiting-for-the-cve-keeps-you-behind/6ad26ccef3e4a1579870c876)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/reactive-security-why-waiting-for-the-cve-keeps-you-behind/6ad26ccef3e4a1579870c876/comment/6ad2b924e3a72cab329d50bb)

The Day 0 to Day 13 timeline makes the argument better than any statistic: the fix existed upstream for twelve days and the dashboard stayed green the whole time. Pairing it with Mandiant's drop in average time-to-exploit to 5 days shows why a CVE-triggered backlog ticket is already too late. Watching upstream release notes for the libraries in an API gateway seems like the cheapest first step toward getting ahead.
