Sophos UTM End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Sophos UTM versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Every tracked Sophos UTM version is past end of life; the most recent to reach it, 9, did so on June 30, 2026. The full Sophos UTM lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/sophos-utm)
Sophos UTM lifecycle status — the real story
Sophos UTM (the Astaro-lineage SG UTM software, major versions 6 through 9) from Sophos's own retirement calendar KBA-000003353 ('Sophos UTM software' table; article dated Sep 03, 2026, read 2026-09-09 in a browser). eol = EOL; the End-of-Life notification date is carried. UTM 9, the last major, reached end of life 30-Jun-2026; Sophos adds that UTM/SG customers with a valid licence are supported until their expiry date or 31 December 2026, whichever comes first, and that no renewals are possible after 31 December 2025. Release dates are not on the page and are left null. The named migration path is Sophos Firewall (SFOS) on XGS hardware.
KEV context (CISA catalog 2026.09.08): CVE-2020-25223 under 'Sophos / SG UTM' (added 2022-03-25), matched on the display name. No version scoping is asserted here.
Sophos UTM release and support pattern
Of the 4 release lines tracked, 4 are past end of life and 0 are still within support.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Sophos UTM security intelligence
CISA KEV history: Sophos UTM is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2022-03-25. Derived from CISA's live catalog at every build.
What does Sophos UTM end of life mean for your organization?
When a version of Sophos UTM reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Sophos UTM should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Sophos UTM reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Sophos UTM versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Sophos UTM has 4 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Sophos UTM is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."