DKDKCISSP
DKCISSP / BLOG

When the Patch Never Comes

SonicWall says its Gen 6 firewalls will never get another security patch, and CISA just flagged an exploited, critical flaw in end-of-life Apache Axis 1.x with no fix coming. How to find and handle the systems that will stay open forever.

By Deepak Kumar, CISSP1 min readOpinion

Most of our security programme rests on one quiet promise: when a serious flaw is found, a patch will come. We argue about how fast to apply it, but we rarely ask what happens when it never arrives.

This week two very different products answered that question. SonicWall told customers its Gen 6 firewalls will get no more security patches, not even for critical flaws, and to pull them off the internet. And CISA added a critical, actively exploited flaw in Apache Axis 1.x to its exploited list, for a library that is end-of-life and will not get a fixed release.

One is a box in your rack. The other is a library buried inside software you bought. Both are now permanently open doors, and attackers know exactly where to look.

SonicWall Gen 6No patchesever again, whatever the severity, says SonicWall
Apache Axis 1.x9.8CVSS, exploited, and no fixed 1.x release planned
Shrinking window80 daysmedian from disclosure to exploitation in H1 2026, down from 120
CISA deadline3 daysfrom adding the Axis flaw (18 Nov) to the federal deadline (21 Nov)
01 · Two kinds of unpatchable

The one you can see, and the one hiding inside something else

VISIBLE: AN APPLIANCE AT THE EDGE The internetAutomated scanners find old firmware fast SonicWall Gen 6 / 6.5 firewallSonicOS 6.x · end of support · no patchesGen 6 already exploited via CVE-2024-40766 Your internal networkEverything behind the firewall trusts it You know it is there. The problem is budget and downtime. HIDDEN: A LIBRARY INSIDE A PRODUCT Software you runAn app, a portal, a management tool A vendor product or componentTrackers list N-able N-central (Legacy API)among the products that needed fixes Apache Axis 1.x, through 1.4CVE-2026-90436 · end of lifeno fixed 1.x release planned You may not know it is there. The problem is finding it.

On the left is the kind of end-of-life risk most teams already track: a firewall with a model number and a support date. It is visible, it is in the asset list, and the hard part is budget and downtime. Because it sits at the internet edge, everything behind it depends on it, which is why SonicWall says to take Gen 6 off the edge now.

On the right is the harder kind. Apache Axis 1.x is a software library, and libraries hide inside other products. You might run it without ever installing it yourself, because a vendor built it into their software years ago. You cannot patch what you cannot find, so the first job is knowing where it lives.

02 · Why “we will replace it next year” no longer works

The gap between disclosure and attack keeps shrinking

2025: median days, disclosure to confirmed exploitation
120
First half of 2026
80

For a supported product, that window is the time you have to patch. For an end-of-life product there is no patch at the end of it, so the window simply never closes. Figures as reported by heise.

Put simply: last year defenders had a median of about four months between a flaw becoming public and attackers using it. In the first half of this year that dropped to under three months. For a supported product, that is your patching window. For an end-of-life product, the same clock runs, but there is no patch waiting at the end.

03 · Decide for one system

What should you do with your end-of-life system?

Answer four questions about one unsupported system you know about.

What is it?
Can the internet reach it?
Is a flaw in it already being exploited?
How soon could you replace it?

The logic is deliberately simple. Anything the internet can reach, especially an edge device or something already being exploited, goes to “act today”. Internal systems you can replace soon can be managed with controls and a firm date. Libraries get an extra step, because the first problem is finding every copy.

04 · When you cannot replace it yet

Compensating controls, in the order I would use them

Sometimes you genuinely cannot replace a system this month: the budget is not there, or a critical process depends on it. That is a real situation, not a failure. What matters is that the risk is reduced, watched and given an end date, in this order.

1 · Today

Take it off the edge

SonicWall’s own advice for Gen 6. If the internet cannot reach it, most automated attacks cannot either.

2 · This week

Lock the management plane

Admin interfaces only from a jump host or trusted IPs. Turn off features you do not use.

3 · This month

Shield and watch it

Segment it, put a WAF or virtual patch in front, and send its logs where someone will read them.

4 · This quarter

Fund the exit

Put a dated replacement in the budget. An exception without an end date is just a risk you forgot about.

05 · Monday morning

What I would put on the board on Monday

Track end-of-life dates like expiry dates

Every asset in the inventory gets an end-of-support date, and someone gets a reminder a year before it.

Ask vendors what is inside

Request a software bill of materials for products you run, so the next Axis is a search, not a hunt.

Report the open doors

Show leadership the list of unpatchable systems with an owner and a date. Risk that is visible gets funded.

A patch you will never get is not a delay. It is a decision.

Running an end-of-life system is sometimes the right call for a short time. But it should be a decision someone signs, with compensating controls and an end date, not something we discover after an attacker does. The firewall is the easy one. Go and find the libraries.

Sources

Facts as reported up to 21 November 2026.

  • End of Life
  • Vulnerability Management
  • Firewalls
  • Opinion
← Back to Blog