Apply mitigations per vendor instructions or discontinue use of the product

In CISA's KEV feed of 19 Nov 2026 (catalog 2026.11.18), 893 of 1,786 entries say only to apply updates, 762 say to apply mitigations or discontinue the product, 83 name an end-of-life product to disconnect, and 48 use other wording. All 302 entries added in 2026 carry a discontinue clause.

  1. Remediate
  2. Mitigate now, fix laterThis page is about it
  3. Accept with a dated exception

Seven wordings in the feed

Counted by script from the CISA KEV JSON feed (catalogVersion 2026.11.18, released 18 Nov 2026) on 19 Nov 2026. Each of the 1,786 entries is in one row, sorted by its requiredAction text in the order of the rows. Rows 2 to 4 are the standard mitigate-or-discontinue strings: 762 entries. Vendor counts are per row and overlap between rows.
Required actionEntriesAdded betweenVendorsDays from added to due date (entries)
"Apply updates per vendor instructions." and nothing else8933 Nov 2021 and 23 Jun 202315021 (441); 181 (235); 14 (192); 182 (11); 184 (8); 31 (4); 24 or 25 (2)
"Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable."26417 Jul 2023 and 24 Feb 20258621 (245); 7 (8); 4 (5); 8 (2); 12 (2); 2 (1); 43 (1)
The same, with "follow applicable BOD 22-01 guidance for cloud services"32910 Oct 2023 and 9 Jun 202612421 (235); 14 (55); 3 (27); 7 (9); 1, 2 and 5 (1 each)
"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04" and forensic triage16911 Jun 2026 and 18 Nov 2026793 (131); 14 (38)
End-of-life product: disconnect, discontinue, remove or retire833 Nov 2021 and 22 Jul 20251921 (71); 14 (6); 1 (3); 181 (3)
Older form: "updates ... or discontinue use of the product if updates are unavailable" (also "remediations or mitigations")2829 Jun 2023 and 8 Oct 20241021 (28)
Other: emergency directive instructions, CISA instructions, contact the vendor, disable a service2010 Dec 2021 and 14 May 2026921 (5); 3 (4); 7 (3); 4 (3); 1 (2); 2 (2); 14 (1)

The word "discontinue" appears in 815 entries: all 762 in rows 2 to 4, 28 in row 6, 15 in row 5 and 10 in row 7. Of the 547 entries added since 1 Jan 2025, 531 are in rows 2 to 4.

The wording changed with the year

From the same feed, read 19 Nov 2026. Other wording combines rows 6 and 7.
Year addedEntriesUpdates onlyMitigate or discontinue (rows 2 to 4)End-of-lifeOther wordingContain "discontinue"
20213113090110
202255549905420
2023187856942995
20241860162186175
2025245023564243
2026302029606302

Through 23 Jun 2023 the standard action was an update. The first discontinue clauses were added on 29 Jun 2023, still worded around updates, and the standard mitigations string starts on 17 Jul 2023. A reader treating KEV as a patch list sees only part of the instruction.

Due dates follow the wording

Across the 815 entries with a discontinue clause, 522 are due 21 days after they were added, 162 after 3 days, 93 after 14 days, 17 after 7 days, 6 after 1 day, 5 after 4 days, 4 after 2 days, 2 each after 8 and 12 days, and 1 each after 5 and 43 days. The newest wording, from 11 Jun 2026, names BOD 26-04 and CISA's forensic triage guidance. Its feed field forensicTriage is "Yes" on 108 entries, every one due in 3 days; of the 61 marked "No", 23 are due in 3 days and 38 in 14 days. The date logic for those entries is in patch available and exposed.

Two entries, one clause, opposite instructions

Both entries were added on 18 Nov 2026 with the BOD 26-04 wording, which ends: "Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable." Both are due 21 Nov 2026, 3 days later, and the feed marks both forensicTriage "Yes". What the vendors say differs.

Entries from the KEV feed and vendor pages, read 19 Nov 2026.
Synology DiskStation Manager, CVE-2024-10441Apache Axis 1.x, CVE-2026-90436
Vendor source in the entry's notesSynology-SA-24:20, published 5 Nov 2024Apache Axis announcement on the java-user list, 6 Nov 2026
FixFixed releases listed, for example DSM 7.2.2-72806-1 or above"The Apache Axis project does not expect to create an Axis 1.x release fixing this problem." A source patch (a commit) exists
Vendor mitigation"Mitigation None"None stated; recommends migrating to another SOAP engine
What "mitigations per vendor instructions" comes toApply the vendor's updateMigrate, or build Axis with the published patch
When discontinuing appliesOnly if the update cannot be installedThe product is end of life, so for most users it is the route

The clause is a template. For Synology, the vendor's only instruction is an update, so the three-day clock is an update clock. For Axis there is no vendor release, so the choice is between a patched build you own and retiring the component. Neither entry offers a mitigation in the sense of a control that leaves the flaw in place.

Choosing, and who decides

  1. Open the source in the entry's notes field. Every one of the 815 entries carries text there: the vendor advisory or CISA guidance the action refers to.
  2. Find your version in that source. If it lists a fixed release or a vendor workaround, that is the action, and the due date is the date to meet. Record the version before and after.
  3. If no fix or workaround exists for your version, choose between a control you own with a dated fix plan (mitigation when no patch exists, no patch yet) and removing the product from service. Discontinuing is closer to the avoid response in NIST SP 800-40 Rev. 4: "uninstalling the vulnerable software, decommissioning assets with the vulnerabilities, or disabling computing capabilities".
  4. If the date cannot be met, the route is to remove the asset from the network; write the exception down.

BOD 26-04 requires each agency's policy to "Assign roles and responsibilities for executing agency actions" and to "Establish internal validation and enforcement procedures". The deciding person is therefore named by the organization's own policy, usually the system owner with the risk owner signing any interim control. The record left behind holds the entry's date added and due date, the source read, the version, the action taken and its date, or the exception and its end date.

Sources

Last reviewed