End-of-life software: replace, isolate or accept

Remediate by replacing or removing the product, because no patch will ship. CISA BOD 26-02, issued 5 Feb 2026, has federal agencies decommission end-of-support edge devices by 5 Aug 2027. NIST SP 800-53 SA-22 allows an exception only for a critical capability with no replacement or for a system too isolated to replace.

  1. RemediateGuidance points here
  2. Mitigate now, fix laterAlso allowed
  3. Accept with a dated exceptionAlso allowed

Signals: Vendor has ended support; No updates exist

The situation

The vendor has ended support, so no update exists or will. NIST puts the cause in one sentence: "The vendor may no longer support the vulnerable software, meaning that a patch for it will never be released because the software is at end-of-life." Every later finding on the product stays open for good, so the decision is about the product, not the single CVE.

The decision and its conditions

Remediate: replace the product with a supported one, or remove it. Mitigate now, fix later and Accept with a dated exception are allowed while the replacement is built. The exception is narrow, and the conditions are these:

  1. A replacement project exists, with a date and an owner.
  2. Until then the product is isolated from public and uncontrolled networks, and the isolation was checked.
  3. If replacement is blocked, the block is one of the two SA-22 reasons below, and the approver signs it.
  4. If the product is a federal edge device, the BOD 26-02 dates are met.

The rules it follows

BOD 26-02 covers edge devices, meaning devices on the network boundary that the vendor or CISA considers end of support. It binds federal civilian agencies, not contractors, and it "does not apply to Operational Technology devices and FedRAMP authorized cloud computing" services. Its dates run from 5 Feb 2026.

BOD 26-02, Required Actions, issued 5 Feb 2026. The right column counts months from the issue date; CISA prints the intervals, not the calendar dates. Read 19 Nov 2026.
DeadlineAction required of federal civilian agenciesDate by count
ImmediatelyUpdate each vendor-supported edge device running end-of-support software to a supported version, where this does not adversely affect mission critical functionality5 Feb 2026
3 monthsInventory devices on the CISA end-of-support edge device list5 May 2026
12 monthsDecommission listed devices whose end-of-support date is on or before the deadline5 Feb 2027
18 months"Decommission all identified EOS edge devices from agency networks, replacing devices as needed with vendor-supported devices that can receive current security updates."5 Aug 2027
24 monthsKeep continuous discovery running and have decommissioned devices on or before their end-of-support dates5 Feb 2028

NIST SP 800-53 SA-22 states when replacement may wait: "Exceptions to replacing unsupported system components include systems that provide critical mission or business capabilities where newer technologies are not available or where the systems are so isolated that installing replacement components is not an option." It adds that the added risk "can be mitigated, for example, by prohibiting the connection of such components to public or uncontrolled networks, or implementing other forms of isolation". Its assessment objects include "documented approvals (including justification) for the continued use of unsupported system components", which is the record to keep.

CISA's KEV catalog shows how often the end-state is removal, not a patch. CISA explains the practice in its guidance: it "does not assume that all running legacy products are fully patched", and "actors will continue exploiting vulnerabilities until they are remediated or mitigated".

Required-action wording in the CISA KEV feed, catalog 2026.11.18 (1,786 entries), counted 19 Nov 2026. None of the 83 entries was added in 2026; 54 were added in 2022.
What the required action tells you to doEntries
Disconnect the product if still in use62
Discontinue use of the product12
Remove the product from service or from agency networks5
Retire and replace the product (legacy D-Link hardware)4
Total with end-of-life wording83

Worked case: CVE-2026-111497 on an end-of-life Node.js line

A flaw in the Brotli decoder bundled in Node.js lets an attacker who controls compressed input corrupt process memory, which can lead to a crash, memory disclosure or remote code execution (CVSS 3.1 base score 9.8 from NVD). A service runs on Node.js 20, an end-of-life line. Node.js 22, 24 and 26 get fixes; Node.js 20 gets none.

CVE-2026-111497, Brotli decoder bundled in Node.js. Read 19 Nov 2026.
DateEventBasis
21 Oct 2026Node.js releases 22.23.4, 24.22.1 and 26.12.1. Its advisory says end-of-life lines (25.x, 23.x, 20.x and earlier) are always affected and get no fixNode.js security release
26 Oct 2026ELLIO records exploitation in the wild at 15:08 UTCELLIO
27 Oct 2026CISA adds the CVE to the KEV catalogCISA KEV feed
10 Nov 2026KEV due date, 14 days after listing. Forensic triage is marked not requiredCISA KEV feed
19 Nov 2026Today: 9 days past the due date for a federal agency whose Node.js 20 service has not movedCounted

There is no patch to wait for, so the remediation is a move to a supported line: 22.23.4 or later, then a rebuild of images and a restart. The stopgap the researchers at Aikido and ELLIO describe is to reject inbound requests with Content-Encoding br at the reverse proxy; the cost is an error for clients that send Brotli request bodies. It does not cover Brotli responses that the service itself fetches from other servers. BOD 26-02 does not set the clock here, because an application runtime is not an edge device; for a federal agency the clock is the KEV due date of 10 Nov 2026. For anyone else it is the date the policy sets.

An SA-22 exception does not fit this service. A supported Node.js line exists, so "newer technologies are not available" is false, and the service is reachable by the attackers who send it requests, so "so isolated" is false too. The honest record is a dated plan to move, with the proxy rule as the interim control.

What to record

  • Product, version, vendor end-of-support date, and the CVE or CVEs that raised the question.
  • The replacement: project, date, owner. For federal edge devices, the BOD 26-02 date that applies.
  • The isolation in place and how it was checked, or the basis for saying the product is not reachable.
  • If replacement is blocked: which of the two SA-22 reasons applies, who approved it and the expiry date. Use the risk acceptance form.
  • The review date. For federal edge devices the dates in the table are the ceiling; no source sets one for other assets, so review no later than the replacement date and earlier if exposure changes.

When the usual answer is wrong

  • Extended support exists. A paid support contract is an alternative source of support under SA-22, and the product stops being end of life for that purpose. Record the contract and its end date.
  • The product is in the KEV catalog. If a patch exists for a supported version, go to patch available and exposed; for a version past support the required action is usually to disconnect or discontinue, and the due date still applies to federal agencies.
  • The product is an OT or medical device. BOD 26-02 excludes OT. Use OT and medical devices, where replacement is often not an option.
  • The stopgap is partial. The Node.js proxy rule covers one path in. If the service also fetches Brotli data from outside, the finding is still open.

How to write the exception when replacement is blocked, and what the feed shows by year, is on accepting risk on end-of-life software.

Sources

Last reviewed