Skip to main content

SonicWall Says Gen 6 Firewalls Will Never Be Patched Again: The Board Question Is Who Owns End-of-Support Risk

6 min read
CISO Daily
SonicWall Says Gen 6 Firewalls Will Never Be Patched Again: The Board Question Is Who Owns End-of-Support Risk

The short version

On 18 November 2026 SonicWall published a product advisory, “Retire Unsupported Gen 6 Firewalls”. It tells every customer still running Generation 6 (Gen 6 and Gen 6.5) firewalls to replace them immediately and stop using them on the internet edge. SonicWall says it no longer releases firmware or security patches for these devices, whatever the severity of a newly found flaw, including critical ones. In SonicWall’s words as we read them, a new flaw stays open permanently on Gen 6.

This is not a new vulnerability. It is a vendor stating in plain terms that a class of perimeter device is permanently unpatched. For executives, the issue is ownership: someone must decide whether to replace these devices, and by when, before something is found in them.

What SonicWall says

The advisory covers every Gen 6 and Gen 6.5 firewall running SonicOS 6.x, including Gen 6 virtual firewalls (NSv 10 to NSv 1600). It lists end-of-support dates by model. Several are recent: the TZ350, TZ500 and SOHO 250 families and the NSA 4600 to 6600 series reached end of support on 1 October 2026, and the TZ400, TZ600 and NSA 3600 on 1 August 2026. Others ended earlier, including the NSA 2600 (8 March 2024) and the TZ300 (23 January 2025).

SonicWall says it expects internet-facing Gen 6 firewalls to be actively targeted (paraphrase) and asks customers to treat any still in service as a high-risk exposure. Its reasoning:

  • Every fix is a map. When a flaw affects several generations, supported firewalls get a fix and Gen 6 does not, so the public advisory shows attackers where to look.
  • A compromised perimeter firewall is a foothold for further attacks (our summary).

SonicWall also cites third-party figures to support its urgency: edge devices and VPNs were the target in 22% of breaches that began with an exploited vulnerability, up from 3% a year earlier (Verizon 2025 DBIR, via Censys), and the median time from disclosure to confirmed exploitation fell from 120 days in 2025 to 80 days in the first half of 2026 (CSO Online, October 2026). These are SonicWall’s citations. We have not checked the underlying reports (Verizon, Censys, CSO Online).

What SonicWall asks customers to do

Identify every Gen 6 firewall, including spares and branch units. Prioritise those exposed to the internet or providing remote access. Replace them with a Gen 8 firewall running SonicOS 8.

Until replacement, SonicWall lists interim steps and says (paraphrase) that they reduce exposure but do not make an unsupported firewall secure: disable WAN management (HTTPS, SSH and SNMP), disable SSL VPN or restrict it to known source addresses, enforce multi-factor authentication on remaining remote-access and admin accounts and reset local passwords, disable unused services, and monitor logs for unusual logins and configuration changes.

Why this belongs on a board agenda

Our assessment, not SonicWall’s: three points make this more than an IT housekeeping item.

It is a decision, not a patch. Patching is routine. Replacing a perimeter firewall means budget, a change window and often a branch-by-branch rollout. If nobody owns that decision, the devices stay in place by default.

Residual risk becomes a risk acceptance. Keeping an unsupported internet-facing device is a choice to carry open-ended risk. That choice should be recorded, owned by a named executive and given an expiry date, not left as an unnoticed inventory line.

Others may ask about it. The advisory does not mention regulators or insurers. Our inference is that supervisors under regimes such as NIS2 or DORA, and cyber insurers asking about end-of-life technology at renewal, could reasonably ask why a vendor-declared unpatchable perimeter device was still in service. We have not seen any such statement tied to this advisory.

Questions for management this week

These are our suggestions, not regulatory requirements.

  1. How many Gen 6 or Gen 6.5 firewalls do we run, and where? Ask for a count by model, site and owner, including those managed by third parties, subsidiaries and recently acquired entities, with a statement of how complete the list is.
  2. Which are internet-facing or provide remote access? SonicWall prioritises these. Ask for a replacement date for each.
  3. What have we done in the meantime? Ask for confirmation, device by device, of the interim steps: WAN management off, SSL VPN off or restricted, MFA enforced, passwords reset, logs monitored.
  4. Who has accepted the residual risk? For any device that cannot be replaced soon, ask for a named executive, a documented rationale and an end date.
  5. Is this a pattern? Ask for the same report on all end-of-support network equipment, from any vendor.

What we could not confirm

  • Method note: sonicwall.com blocks scripted requests. Our drafting agent reported reading the advisory in full; our reviewer could only read it through a summarising tool. Where we paraphrase SonicWall above, check against the live page.
  • We found no evidence as of 21 November 2026, in the SonicWall advisory, of exploitation of a new Gen 6 flaw. SonicWall’s statement that it expects exploitation is a forecast.
  • The advisory refers to the 2024 flaw CVE-2024-40766. Our checks of NVD and CISA KEV (21 November 2026): NVD describes it as affecting Gen 5 and Gen 6 devices, and Gen 7 devices running SonicOS 7.0.1-5035 and older. It is in CISA KEV (added 2024-09-09, ransomware campaign use marked “Known”). The 9.3 score is from SonicWall as CNA; NVD’s own score is 9.8. KEV does not say which generations were hit, and “affected” is not the same as “targeted”. We did not open SonicWall’s own advisory for that CVE.
  • The Verizon, Censys and CSO Online figures are SonicWall’s citations; we did not open the underlying reports.
  • End-of-support dates were checked only against the advisory’s table, not SonicWall’s Product Life Cycle tables.

Sources