CISA Gave 9 of 16 November KEV Entries a Three-Day Deadline With Forensic Triage, and 7 Got 14 Days
Security / analysis
CISA Gave 9 of 16 November KEV Entries a Three-Day Deadline With Forensic Triage, and 7 Got 14 Days
The catalog's own due-date and forensicTriage fields show two tiers under BOD 26-04. Sorting November's additions by tier shows which exploited bugs CISA treats as already-compromised-until-proven-otherwise.

Between Nov. 3 and Nov. 17, CISA added 16 vulnerabilities to its Known Exploited Vulnerabilities catalog. Nine came with a three-day federal deadline and a forensic-triage requirement. The other seven came with 14 days and no triage. The split is visible in two fields of the catalog's JSON feed, dueDate and forensicTriage, and it says more about how CISA reads each bug than the headline CVSS scores do.

The figures below were computed from the catalog feed (version 2026.11.17, 1,782 entries, released at 17:53 UTC on Nov. 17). CISA's directive page returned an access error to this report's retrieval, so the rules behind the tiers come from Nucleus Security's reproduction of the BOD 26-04 timeline table and should be checked against the directive itself.
The two tiers, entry by entry
- 3 days plus forensic triage9 entries
- 14 days, no triage7 entries
Source: CISA KEV catalog JSON, version 2026.11.17, accessed 2026-11-17
| Tier | Entries (date added) |
|---|---|
| 3 days, triage | WordPress Core CVE-2026-119977 (Nov. 3); GPUStack, OpenSSH, FreeSWITCH, IBM Aspera Faspex (Nov. 9); two Barracuda entries (Nov. 10); UnrealIRCd, Check Point (Nov. 13) |
| 14 days, no triage | Apple CVE-2024-27834 (Nov. 4); SonicWall SonicOS SSLVPN (Nov. 6); Outlook, Openwave Webtop, Cisco BroadWorks, Chromium (Nov. 10); Puppet Enterprise (Nov. 17) |
All nine three-day deadlines have already passed as of Nov. 17. The last two, UnrealIRCd and Check Point, fell due on Nov. 16.
What the tiers appear to encode
Nucleus Security's table sorts every KEV entry by four questions: is the asset publicly exposed, is the CVE in KEV, can exploitation be automated, and does it give total or partial control. Three rows carry "3 days + forensic triage", and each combines KEV listing with total control. No partial-control row carries triage, and in the table's KEV rows partial control mostly means 14 days.
The November pattern fits that reading, though CISA does not publish its per-CVE reasoning. Two of the 14-day entries plausibly sit in the partial-control bucket. The Outlook flaw, CVE-2026-124194, discloses a password hash, and the Chromium use-after-free, CVE-2026-125350, runs code inside the browser sandbox according to the CISA entry. The three-day entries read like total-control bugs: an authentication bypass granting administrator access in GPUStack, and command injection in FreeSWITCH.
The inference is this report's, not CISA's. If a 14-day entry later turns out to have been chained to a full compromise, the tier will have been wrong, and the catalog has no field to say so.
What triage means in practice
eSecurityPlanet's report on the Nov. 9 batch gives the working detail. It says upgrading GPUStack does not revoke administrator API keys an attacker already created, so a team that patches by Nov. 12 and stops there still has the intruder's access. It also says systems running vulnerable versions may have been compromised before the warning.
That is the logic of the triage flag. The deadline is for the patch; the triage is for the question of whether the patch came too late.
The same report flags a mismatch in one three-day entry. IBM's bulletin for Aspera Faspex CVE-2026-123218, affecting 5.0.0 through 5.0.19 and fixed in 5.0.19 PL1, describes an authenticated user, while the CVSS vector says no privileges are required. IBM does not explain the difference.
What the Nov. 9 batch shows
The four Nov. 9 entries make the tier concrete. GPUStack versions before 2.2.0 have an authentication bypass that can grant administrator access, reachable through certain reverse-proxy setups or a manipulated X-GPUStack-Real-IP header. FreeSWITCH 1.11.2 and earlier has command injection in SIP MESSAGE handling, rated CVSS 9.8 and fixed in 1.11.3.
The OpenSSH entry is narrower: authentication bypass on Linux systems using musl libc without PAM, which includes some Alpine Linux setups. All four have confirmed exploitation, per eSecurityPlanet, but CISA has not named attackers or said how many organisations were hit.
Why three days at all
Three days is short, and the attacker side is faster still. The FBI's warning about the Artex tool describes criminals going from scan to breach in under three hours. Google's threat group, in its exploit_agent report, describes an agent that diffs a patch and fires an exploit with no operator. Against that, a 72-hour federal window is slow, and a 14-day one is generous.
CISA's catalog marks known ransomware campaign use as Unknown for all 16.
What applies outside the federal government
The deadlines bind federal civilian agencies only. eSecurityPlanet says private organisations are not bound but are advised to prioritise remediation. The practical use for everyone else is the tier itself: an entry with a triage flag is CISA saying that patching is not enough to close the incident.
For a team triaging a week of KEV additions, that gives an order. Handle the nine triage-flagged products first, and for each ask whether credentials, keys or accounts created before the patch still work. Then take the 14-day entries by exposure.
The next entries to watch are the 14-day ones. Outlook and Chromium fall due on Nov. 24 and Puppet Enterprise on Dec. 1. If CISA moves any of them to a triage tier, or a ransomware flag changes from Unknown, the catalog JSON will show it.
Sources
More in Security
- 01Java4Shell Scores 9.2 From Its Finder and 8.1 From OpenJDK, and Needs an AVX-512 CPUCalif says a 65-character Base64 string overwrites 62 bytes of Java heap and reaches code execution in Keycloak, Jenkins and Jira. A second security firm says the source shows only a crash.
- 02Project Zero Cuts Its Disclosure Deadline to 60 Days on Feb. 2, 2027, Then 30 in 2028Google's bug-hunting team is dropping the 30-day patch soak period and counting every deadline from the day it reports, citing AI-assisted exploitation.
- 03Google Finds exploit_agent Diffing Patches and Firing Exploits With No Operator in the LoopGTIG's November 16 tracker reports the first fully automated discovery-to-exploit pipeline it has seen, found on an exposed staging server, plus 22 zero-days in August.
- 04Mandiant: LLMjacking Runs Up $100,000 a Day on Stolen Cloud Keys, and Logs Are Off by DefaultGoogle's Nov. 2 report says single-token test calls evade volume alerts, and it describes the LiteLLM bug differently from BleepingComputer.