Published 16 November 2026 · Rathish Kumar, Invitty
Sophos has fixed CVE-2026-98432, a Linux kernel TCP flaw, on its firewalls and RED units. Hotfix HF110626.1 (6 November 2026) covers SFOS v22.0 MR3, v23.0 GA and v23.0 EAP1, and it only takes effect after a restart. SD-RED 20 and SD-RED 60 need firmware 3.0.012, which reached Sophos UTM as a manual patch on 10 November. Restart your firewall in the next maintenance window, then confirm the hotfix shows as installed.
What Sophos published, and when
The advisory, sophos-sa-20261102-linux-kernel-tcp, first went up on 2 November and has been revised several times since. The copy we read on 16 November was version 5, last updated 12 November. The bug is not specific to Sophos. It is a use-after-free in the IPv4 TCP code of the Linux kernel, and every appliance built on that kernel inherits it. That is why Veeam also had to ship kernel updates for the same CVE this month, which we covered in our Veeam appliance post.
Scoring is split. The Linux kernel CNA gives it 9.8 on CVSS 3.1. Red Hat scores it 5.9, because an attacker has to win a race condition to trigger it. Sophos lands in between and calls it High. Sophos says an unauthenticated attacker could, under specific conditions, run code with kernel privileges. The lab demonstration targeted a Linux server with a Multipath TCP listener, not a Sophos box. Sophos says it has seen no public reports of exploitation in the wild. There is no workaround for the appliances, so the fix is the only answer.
Which Sophos products need action?
Three product families are listed as affected: Sophos Firewall, Sophos RED and Sophos UTM. Here is what applies to each, as of the 12 November revision.
| Product | Version you run | Fix | Released |
|---|---|---|---|
| Sophos Firewall | v22.0 MR3, v23.0 GA, v23.0 EAP1 | Hotfix HF110626.1, restart required | 6 Nov 2026 |
| Sophos Firewall | Any other SFOS version | Upgrade to v22.0 MR3 or v23.0 first, then take the hotfix | No separate hotfix listed |
| SD-RED 20 / SD-RED 60 on SFOS | SFOS 20.0 MR3+ or 21.0 MR1+ | RED firmware 3.0.012 as a pattern update | 5 Nov 2026 |
| SD-RED 20 / SD-RED 60 on UTM | UTM 9.724 or later | RED firmware 3.0.012 as a manual patch | 10 Nov 2026 |
| Legacy RED models | Any | None. End of life, stays vulnerable | n/a |
Note the second row. If your XGS is still on v21.5 or v22.0 MR2, there is no hotfix waiting for it. You need a firmware upgrade first, and that is a bigger change window than a hotfix restart. Sophos also says it is still checking its other products, so read the advisory again before you close the ticket.
How to apply and verify the hotfix
Sophos turns automatic hotfix installation on by default, so most firewalls will already have downloaded HF110626.1. Downloaded is not the same as protected. The new kernel only runs after a reboot, and a firewall that has sat for ten days with a pending restart is still exposed. This is the step we see skipped most often.
- Take a configuration backup and make sure you have a way in that does not depend on the VPN you are about to drop.
- Check the firmware version. If it is not one of the three hotfix targets, plan the upgrade as its own job, then come back for the hotfix.
- If auto-hotfix is off, enable it from the Device Console with
system hotfix enableand wait for the download. - Restart in a maintenance window. Traffic stops while the box reboots, so warn users.
- Verify from the CLI with
system hotfix list. HF110626.1 should show the status Installed. On v23.0 the security updates page in the web console can stay blank even when the fix is in, so trust the CLI. - Test what the business uses: internet, DNS, tunnels, remote access and published servers.
These steps follow Sophos's installation notes, as summarised by Sophos partner Avanet. For a high-availability pair, both units need the fix. Restart the auxiliary unit first, wait for the cluster to report healthy again, then restart the primary.
Do not forget the RED boxes at branch sites
The firewall hotfix does nothing for SD-RED units. They run their own firmware. On SFOS, open Backup & Firmware, then Pattern Updates, check that the RED firmware shows 3.0.012, and use Install to push it to connected devices. Each RED restarts as it updates, which drops that branch for a few minutes.
If you still have older, pre-SD RED units in branches, this advisory is the clearest signal yet. Sophos calls the legacy models end of life and will not fix them. A device that terminates your branch tunnel and cannot be patched against a kernel bug should move to the replacement list for this financial year, not the next one.
What this means for renewals and budgets in India
The hotfix itself costs nothing. The cost sits in the boxes that cannot take it. Two patterns show up when we audit Sophos estates for Indian SMBs. The first is an XGS whose subscription lapsed a year ago and still runs a 2024 build. The second is a branch full of legacy RED units nobody remembers buying. Both need money, not just a maintenance window.
If your firewall licence is close to expiry, sort the renewal out in the same exercise, so you are not chasing a quote in the middle of an upgrade. Ask for a GST invoice that lists the serial numbers covered; it makes the next audit easier. CERT-In's six-hour rule covers incidents, not patching, but a dated record of when each device was fixed is good evidence of diligence. Our renewals team can pull the expiry dates for every Sophos serial you own.
Next step
Send us a list of your Sophos firewalls and RED units with their firmware versions, or a screenshot of the Central device list. We will tell you which boxes can take HF110626.1 today, which need an SFOS upgrade first, and which RED units are past end of life. If replacements make sense, we can quote Sophos XGS firewalls and current RED hardware, or check renewal dates through our Sophos page.
Questions about the Sophos CVE-2026-98432 fix
Is CVE-2026-98432 being exploited on Sophos firewalls?
Our firewall downloaded the hotfix automatically. Are we protected?
We run SFOS 21.5. What should we do?
Does the firewall hotfix also fix our SD-RED devices?
Not sure if your devices are affected? Send us the model and current firmware or version on WhatsApp, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.
Sources
Facts in this post come from these pages, checked on 16 November 2026. Sophos revises its advisories as fixes arrive, so confirm the version list on the advisory before you schedule work.
- Sophos security advisory sophos-sa-20261102-linux-kernel-tcp (CVE-2026-98432)
- Sophos Community: Sophos Firewall hotfix for CVE-2026-98432
- Sophos Community: SD-RED firmware 3.0.012 pattern released
- Avanet: Sophos Firewall kernel hotfix for CVE-2026-98432 (installation walkthrough)
- Ubuntu security tracker: CVE-2026-98432 technical description