---
title: "Discussion on \"Twenty got three days. Eight got fourteen. Your patch queue's sort key was already free — and it's a date.\" | Hashnode"
description: "Discussion on \"Twenty got three days. Eight got fourteen. Your patch queue's sort key was already free — and it's a date.\". CISA's KEV catalog publishes no CVSS score. It publishes a `dueDate`. Between September 1 and 18, 2026 that one field split 28 CVEs into 20 three-day and 8 fourteen-day, and all ten security and remote-management products landed in the three-day pile. Here is how to read the field, why a Cisco-rated 10.0 and an Acronis-rated 7.8 drew the same deadline, and the one-afternoon inventory that turns it into a queue."
url: "https://hashnode.com/posts/kev-due-date-is-the-sort-key/6ab6dc87f1fda2353dd5d21f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Twenty got three days. Eight got fourteen. Your patch queue's sort key was already free — and it's a date.](https://thesecuritygator.hashnode.dev/kev-due-date-is-the-sort-key?utm_source=hashnode&utm_medium=feed)

CISA's KEV catalog publishes no CVSS score. It publishes a \`dueDate\`. Between September 1 and 18, 2026 that one field split 28 CVEs into 20 three-day and 8 fourteen-day, and all ten security and remote-management products landed in the three-day pile. Here is how to read the field, why a Cisco-rated 10.0 and an Acronis-rated 7.8 drew the same deadline, and the one-afternoon inventory that turns it into a queue.

Sep 25 · 14 min read · thesecuritygator.hashnode.dev  
Read the article

-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#security](https://hashnode.com/tag/security)
-   [#devops](https://hashnode.com/tag/devops)
-   [#sysadmin](https://hashnode.com/tag/sysadmin)
-   [#automation](https://hashnode.com/tag/automation)

## Written by

[Gary Austin](https://hashnode.com/@BigG-TheCreator)

@BigG-TheCreator · Earlington, KY

  
[View profile](https://hashnode.com/@BigG-TheCreator)

Founder, The Security Gator — I build AxiomLens: board reports, client hand-offs, and insurance-ready evidence, computed and owned locally .

The Security Gator writes practical GRC for the people who actually do the work — vCISOs, MSPs, MSSPs, and the one-person security team. Weekly field notes on vendor risk, shadow AI, and the mechanics of a security practice: board reports, client hand-offs, evidence that survives an underwriter's email. Written by BigG, founder of The Security Gator LLC and builder of AxiomLens — the GRC command deck you own outright. Locally owned, your data in your hands, one-time license, no monthly rent on your own posture. Free field kits live on the Gatorbyte shelf at thesecuritygator.com; articles here mirror the originals.

## Responses 1

Markdown supported · ⌘↵ to post

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Sep 26](https://hashnode.com/posts/kev-due-date-is-the-sort-key/6ab6dc87f1fda2353dd5d21f/comment/6ab75dca42921770c61ddf70)

One thing worth flagging on the "filter the feed on product" step: CISA's own JSON has no CPE or other stable identifier, just free-text vendorProject and product fields, and the split is inconsistent enough to trip up a plain substring search. In the raw feed, N-able N-central comes back as vendorProject "N-able", product "N-central" (not "N-able N-central"), Cisco Identity Services Engine is vendorProject "Cisco", product "Identity Services Engine", and Acronis Backup is vendorProject "Acronis", product "Backup" - a single generic word, on its own, that would just as easily match some other vendor's product also called "Backup" in a bigger asset list. Searching product alone either misses real hits (your inventory string like "Acronis Backup" doesn't appear anywhere in that field) or risks picking up unrelated ones (a one-word product name matching something you don't actually run). Matching on vendorProject plus product together seems safer than either field alone, otherwise the five-minute version of this exercise turns into an afternoon reconciling what actually matched.
