P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

SonicWall says Gen 6 firewalls get no patches, even for Critical flaws; its end of support dates span 937 days

SonicWall's notice of 18 November 2026 says it releases no patches for Gen 6 firewalls whatever the severity, Critical included. Its table has twelve rows and seven end of support dates, 937 days apart (derived). Read 20 November 2026: what it states and leaves out.

By · LinkedIn · · 15 min read

Twelve table rows, seven end of support dates, 937 days from first to last

SonicWall's product advisory Retire Unsupported Gen 6 Firewalls is dated Wednesday 18 November 2026: the page prints both PUBLISHED and LAST UPDATED as November 18, 2026. This site saved it at 15:20 UTC on Friday 20 November, two days later (derived). The notice advises customers to "replace them immediately and to stop using them on the internet edge", and says "SonicWall no longer releases firmware updates or security patches for Gen 6, whatever the severity of a newly found vulnerability, including Critical."

Its table is the checkable part. It has twelve rows of models, and the rows carry seven distinct End of Support dates, not twelve (derived: count of rows and of distinct dates). The earliest is 8 March 2024, for the NSA 2600. The latest is 1 October 2026, for three rows. Those two dates are 937 days apart (derived: 730 days from 8 March 2024 to 8 March 2026, plus 207 days to 1 October 2026). The latest date is 48 days before the notice (derived: 30 days left in October after the 1st, plus 18 in November), and the earliest is 985 days before it (derived). The notice says "All listed models have reached End of Support", and no date in the table is later than the notice's own.

What that does not establish. The notice gives no count of Gen 6 firewalls in service anywhere. It names no vulnerability that is open on Gen 6 today. It reports no exploitation of Gen 6 firewalls since support ended: it says "We expect internet-facing Gen 6 firewalls to be actively targeted", which is an expectation, not an observation. It does not say when SonicWall decided any of the dates, or why it published on 18 November. It does not say whether firmware stopped on each model's own date or only now. And it points to SonicWall's Product Life Cycle tables for the dates, which this site did not read.

What the notice tells the reader, and how it argues

The instruction is plain. Replace Gen 6 firewalls "immediately", stop using them on the internet edge, and migrate to "a supported Gen 8 firewall running SonicOS 8". The notice says to treat any Gen 6 firewall still in service as a "high-risk exposure". Its summary line is "An end-of-life firewall that is still running is not a firewall that can still be secured." The notice uses "End of Support" in its table and "end-of-life" in that line, and does not define either.

The argument has four parts, each attributed in the notice itself. This site did not read any of the sources the notice cites.

  • Edge devices are targets. "Edge devices and VPNs were the target in 22% of breaches that began with an exploited vulnerability, up from 3% a year earlier", attributed to "Verizon 2025 DBIR, via Censys".
  • Exploitation is faster. The median time from disclosure to confirmed exploitation "fell from 120 days in 2025 to 80 days in the first half of 2026", and "141 flaws were exploited from January to August 2026", attributed to CSO Online, October 2026. The notice also says attackers use "automation and AI" to find unsupported devices and build exploits.
  • For Gen 6 specifically. "No patches, ever. Any new flaw, even a Critical one, stays open permanently on Gen 6." And "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 "tells attackers where to look".
  • A past example. The notice says a critical SonicOS flaw in 2024, CVE-2024-40766 with a score of 9.3, affected Gen 5, Gen 6 and early Gen 7 firewalls and "was reported as exploited in the wild", citing Help Net Security. That is the only vulnerability id in the notice, and the only SonicWall flaw it reports as exploited. It is a 2024 event on supported firmware, not an observation about Gen 6 after end of support. The other exploitation figures in the notice are general ones, about the industry, not about Gen 6.

The notice also says "SonicOS 8 has been hardened with frontier AI-assisted security testing" and that SonicOS 6.x "has not". It prints no test report, no finding count and no method, so that sentence is SonicWall's claim and nothing here can check it. The Help Net Security article this site saved does not mention the 2024 flaw, so the notice's citation points to some other Help Net article (this site's reading).

Diagram 1 draws the table's seven dates on one time axis, with the notice on the right. The gaps between dates, in days, are 321, 393, 55, 15, 92, 61 and 48 (derived), which add to 985. Five of the seven dates fall in 2026, and 31 of the 34 named models are on them (derived, see below).

Drawn from the table in SonicWall's notice as saved on 20 November 2026. Positions come from one time scale. Days before the notice are derived.

The table, grouped by date, and what the labels cover

Diagram 2 reproduces the twelve rows as the notice prints them, with the generation label the notice gives each row and the days to the notice. Table 1 groups the same rows by date.

Models and generation labels copied from the table in SonicWall's notice as saved on 20 November 2026. The days column is derived.

Table 1. The notice's End of Support dates, newest first, with the rows and models printed under each. Days before the notice of 18 November 2026 are derived.

End of SupportRows and models, as printedDays before notice
1 October 20263 rows: TZ350, TZ350W, TZ500, TZ500W, SOHO 250, SOHO 250W; NSA 4600, NSA 5600, NSA 6600; NSa 4650, NSa 5650, NSa 665048
1 August 20262 rows: TZ400, TZ400W, TZ600, TZ600P, NSA 3600; NSa 3650109
1 May 20261 row: NSa 2650201
16 April 20262 rows: SOHO, SOHO W, TZ300P, NSa 9250, NSa 9450, NSa 9650; NSv 10 to NSv 1600 (Gen 6 virtual)216
20 February 20262 rows: SuperMassive 9200, 9400, 9600, 9800; NSsp 12800, NSsp 12400271
23 January 20251 row: TZ300, TZ300W664
8 March 20241 row: NSA 2600985

Counted from the table (derived): twelve rows, seven dates, and 34 named models, with the NSv row counted separately because it prints a range, "NSv 10 to NSv 1600", and no list. Ten rows are dated in 2026 (31 named models plus the NSv range) and two before it: TZ300 and TZ300W on 23 January 2025, and the NSA 2600 on 8 March 2024. The three rows dated 1 October 2026 hold 12 of the 34 named models, and the five rows dated 1 August or later hold 18. The row labels are six "Gen 6", four "Gen 6.5" and two "Gen 6 / 6.5". No row is dated after the notice.

Two label points. First, the notice's opening sentence speaks of "Generation 6 (Gen 6)" firewalls, while its scope sentence says it "covers every Gen 6 and Gen 6.5 firewall running SonicOS 6.x". Four table rows (NSa 4650 to 6650, NSa 3650, NSa 2650, and NSsp 12800 and 12400) carry only the Gen 6.5 label. A reader looking for "Gen 6" in the first sentence alone could miss them; the scope sentence and the table cover them. Second, the scope is defined by software ("running SonicOS 6.x") and the table by model name. The notice does not say what applies to a listed model that runs other software, or to an unlisted model that runs SonicOS 6.x.

What the notice states, and what it does not

Diagram 3 puts the notice beside the Help Net Security article, the one secondary this site saved. Dashed cells are points on which the page prints nothing. Table 2 gives the same split as a stated and not stated list for the notice alone.

Drawn from the SonicWall notice (saved 15:20 UTC) and the Help Net Security article of 19 November 2026 (saved about 15:26 UTC), both on 20 November 2026. Dashed cells mark what a page does not print.

Table 2. What SonicWall's notice states and does not state, as saved on 20 November 2026. Quotations are exact.

PointStated in the noticeNot stated
Patches"SonicWall no longer releases firmware updates or security patches for Gen 6", for any severity, "including Critical"The date firmware last shipped for each model; whether any model got an update after its own End of Support date
An exceptionFAQ: "SonicWall will not release firmware updates or security patches for Gen 6, regardless of severity"Whether any flaw is open on Gen 6 right now
Support contractsFAQ: "Support for Gen 6 can no longer be purchased or renewed"Whether any other arrangement exists; the notice says none, and this site does not add one
Exploitation"We expect internet-facing Gen 6 firewalls to be actively targeted"; one 2024 flaw "reported as exploited in the wild"Any exploitation of Gen 6 since end of support; any victim count
ScaleA table of models and datesHow many Gen 6 firewalls are in service; how many customers
ReplacementGen 8 running SonicOS 8; partner to plan; settings migrate "with the in-product import or the NSM Migration App"A price, a trade in offer, a delivery time, or how a SonicOS 6.5 setting that does not migrate is handled
Interim stepsFive steps, quoted in the technical section below; "They do not make an unsupported firewall secure."Which steps apply to a model with no SSL VPN; any log events or indicators to look for
TimingPublished and last updated 18 November 2026; dates "per the SonicWall Product Life Cycle tables"When SonicWall decided; why 18 November; what changed that day

The friendly name to watch here is "End of Support". It sounds like a date on which something stops being provided. On the notice's own words it also means the reverse of a switch-off: the firewalls keep running, and the notice says a running Gen 6 firewall "is not a firewall that can still be secured". The sentence "A working firewall is not a secure one" appears in the notice's FAQ.

Where the pages differ, with nothing resolved

Four differences between the pages, and one against an earlier brief, are listed below as printed. None is resolved here.

Table 3. Differences between the notice and Help Net Security, and against this site's earlier GMS brief. Reported as printed; none resolved.

PointSonicWall noticeHelp Net Security, or the earlier brief
The statisticsPrints the Verizon figures, 22% against 3%, with "via Censys", and the CSO Online figures (120 to 80 days; 141 flaws)Help Net prints the 22% and 3% and cites "the Verizon 2025 DBIR report", with no Censys; says the time to exploitation fell "drastically" with no figures
"Every fix is a map"Printed in the noticeHelp Net quotes it, and quotes "any new flaw, even a Critical one, stays open permanently on Gen 6". Both are in the notice
Severity wordingTwo wordings: "whatever the severity of a newly found vulnerability, including Critical" and, in the FAQ, "regardless of severity"Help Net quotes only "regardless of severity". It is a quotation of the FAQ wording, not a different claim
Who flagged whatPrints no CISA statementHelp Net says CISA "flagged three vulnerabilities" used against SonicWall firewalls in about two years. This site saved no CISA page and does not check it
Scope against the migration lineScope: Gen 6 and Gen 6.5 "running SonicOS 6.x"The migration answer says settings migrate "from SonicOS 6.5"; Help Net repeats it. Neither says what happens to settings from other 6.x releases
Table dates against the sentenceThe sentence says "All listed models have reached End of Support"; every date in the table is on or before 1 October 2026 (derived)No model has a date after the notice. This site found none to list

Against the earlier GMS brief. this site's brief on SonicWall's end of life GMS notice covered a different kind of notice. SonicWall advisory SNWLID-2026-0019 named two flaws in its end of life GMS console, an unauthenticated file read rated 9.1 and an authenticated SQL injection rated 6.8, and said no fix would come and that there was no workaround. That was a named flaw with an identifier and a score. This notice names no open flaw. It states a standing policy: no patches for any flaw found from now on, at any severity, across every Gen 6 and Gen 6.5 firewall in the table. One tells a customer what is wrong today and will not be fixed. The other tells a customer that whatever is found later will not be fixed either.

What to do, in order

First, what SonicWall says: replace Gen 6 firewalls immediately, stop using them on the internet edge, and migrate to Gen 8 running SonicOS 8. Everything marked as this site's suggestion below does not come from the notice. It is written knowing the notice prints no count of devices and no open flaw.

Take this with you

A checklist for anyone who runs SonicWall firewalls

  • Inventory every SonicWall: model and generation. The notice says to identify every Gen 6 firewall, "including spares and branch units", and its table lists the models. Match each unit against Table 1, including Gen 6.5 models.
  • Treat any unit that matches as unsupported: the notice says no future firmware update or security patch, for any severity, and that support cannot be bought or renewed.
  • Plan replacement by exposure, as the notice says: units exposed to the internet or providing remote access (SSL VPN, WAN management) first. Then branch units, spares and anything not on the internet edge (this site's suggestion on the order after the first group).
  • Until a unit is replaced, apply the notice's interim steps: disable WAN management, disable SSL VPN or restrict it to known source addresses, enforce multi factor authentication on remote access and admin accounts and reset local passwords, disable unused services and interfaces, and monitor logs for unusual logins, configuration changes and traffic. The notice says these steps "do not make an unsupported firewall secure". Source address restrictions and a log review plan are this site's additions.
  • Put an end of support date in your register for every edge device, not only SonicWall, with the date the vendor stopped patching (this site's suggestion).
  • Ask whether any flaw already open on Gen 6 is documented in the vendor's advisories or the public record. The notice names none, so the answer needs a source you check yourself (this site's suggestion).
  • Ask your partner what replacement costs and how long it takes, before you choose a date. The notice prints neither (this site's suggestion).

The table and the interim steps, as the notice prints them

The notice prints no indicators of compromise, no log events to hunt, no detection rules, no configuration commands and no vulnerability ids for Gen 6 beyond the 2024 flaw it mentions as history. This site prints none. What it prints that a defender can use is the model table and the five interim steps. Both are copied as saved on 20 November 2026.

The first block is the table, one row per line, as model, generation label, End of Support date. Use it to match an inventory. Rows are in the notice's order.

Text
TZ350, TZ350W, TZ500, TZ500W, SOHO 250, SOHO 250W | Gen 6 / 6.5 | October 1, 2026
NSA 4600, NSA 5600, NSA 6600 | Gen 6 | October 1, 2026
NSa 4650, NSa 5650, NSa 6650 | Gen 6.5 | October 1, 2026
TZ400, TZ400W, TZ600, TZ600P, NSA 3600 | Gen 6 | August 1, 2026
NSa 3650 | Gen 6.5 | August 1, 2026
NSa 2650 | Gen 6.5 | May 1, 2026
SOHO, SOHO W, TZ300P, NSa 9250, NSa 9450, NSa 9650 | Gen 6 / 6.5 | April 16, 2026
NSv 10 to NSv 1600 (Gen 6 virtual) | Gen 6 | April 16, 2026
SuperMassive 9200, 9400, 9600, 9800 | Gen 6 | February 20, 2026
NSsp 12800, NSsp 12400 | Gen 6.5 | February 20, 2026
TZ300, TZ300W | Gen 6 | January 23, 2025
NSA 2600 | Gen 6 | March 8, 2024
From the SonicWall notice Retire Unsupported Gen 6 Firewalls, saved on 20 November 2026 at 15:20 UTC. Columns: models, generation, End of Support.

The second block is the notice's interim list, under its own line: "These steps reduce exposure. They do not make an unsupported firewall secure." A defender applies them in this order only if no better order is known; the notice does not rank them.

Text
1. Disable WAN management (HTTPS, SSH and SNMP on WAN interfaces).
2. Disable SSL VPN, or restrict it to known source addresses.
3. Enforce multi-factor authentication on every remaining remote-access and admin account, and reset local passwords.
4. Disable services and interfaces you do not use.
5. Monitor logs closely for unusual logins, configuration changes and traffic.
From the SonicWall notice, section Until a Gen 6 firewall is replaced, saved on 20 November 2026 at 15:20 UTC.

The question the notice leaves open

SonicWall has told every Gen 6 and Gen 6.5 customer that the next critical flaw will stay open, and has dated its end of support across 937 days, from March 2024 to October 2026. So which of your firewalls has been without a patch path the longest, and does anyone in your organisation know its date?

Key facts

Sources

  1. PrimaryProduct Advisory: Retire Unsupported Gen 6 Firewalls, published and last updated 18 November 2026 per the page: the notice text, the table of models with End of Support dates, the reasons, required actions, interim steps and FAQ. Rendered copy read at 15:20 UTC on 20 November 2026; the primary for every quotationSonicWallaccessed 2026-11-20
  2. Reported bySonicWall urges customers to replace Gen 6 firewalls now, 19 November 2026: a secondary that quotes the notice; used to compare wording and for its own addition on CISA, and attributed where quoted. Read at about 15:26 UTC on 20 November 2026Help Net Securityaccessed 2026-11-20

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.