Sophos says a remote attacker with no account can run commands with root privileges, which makes it a remote code execution flaw. The attacker must first win a race condition, by repeating attacks for a few minutes, when the email proxy is used with scanning enabled. Sophos rates it Critical, lists all UTM versions as affected and published a manual patch on 28 October 2026.
What it allows
Sophos describes a path traversal flaw in Sophos UTM. A remote attacker with no account can run arbitrary commands with root privileges, but only after winning a race condition. The attacker does that by sustaining repeated attacks for a few minutes, when the email proxy is used with scanning enabled. A race condition is a timing bug: the outcome depends on which of two actions finishes first, so the attacker keeps trying until one attempt lands.
Sophos rates the advisory Critical and lists no workaround. The CVE record carries two scores, both set by Sophos as the CVE assigner: CVSS 4.0 base 9.2 Critical, and CVSS 3.1 base 8.1 High with the vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Sophos lists the weakness as CWE-35 in the CVE record, and NVD has not scored the record itself.
Sophos credits the external researcher Sam Pizzey, who reported the flaw through the Sophos bug bounty program. The advisory does not say whether the flaw is exploited. CISA's Known Exploited Vulnerabilities catalogue, version 2026.10.28, does not list the CVE (checked 28 October 2026).
Who is affected
Sophos lists Sophos UTM, all versions, as affected. The NVD record, filled in by Sophos, names the product SG UTM and the affected versions as everything up to and including 9.724. That is also the release Sophos tells owners to install before the patch, so the patch is a separate step on top of it.
Sophos' patch article applies to a UTM set up as an SMTP gateway. The advisory says customers still using Email Protection features should patch as soon as possible, and that the flaw is reached through the email proxy with scanning enabled.
Sophos says UTM is past its 30 June 2026 end-of-life date, so the patch must be installed by hand. Sophos Firewall is a different product, and the advisory does not list it as affected. The older CVE-2022-3236 flaw in Sophos Firewall is about that product and unrelated.
Timeline
-
30 Jun 2026
Sophos UTM reaches its end-of-life date, according to a Sophos community post of 28 October 2026.
-
28 Oct 2026
Sophos publishes advisory sophos-sa-20261028-utm-rce and the patch article KBA-000049692. The advisory says an external researcher reported the flaw through the Sophos bug bounty program and that it is fixed.
-
28 Oct 2026
The CVE and NVD records are published, NVD at 19:17 UTC. NVD shows the status Received and carries the scores set by Sophos.
What to do
-
Find the UTM appliances that handle mail
List every Sophos UTM and note any set up as an SMTP gateway or using the email proxy with scanning. Sophos' patch article applies to a UTM set up as an SMTP gateway.
-
Update to version 9.724
Sophos' patch article starts with updating the UTM to the latest version, 9.724, if it is not already there.
-
Install the RPM patch by hand
Follow KBA-000049692: download the RPM from Sophos, check its SHA256 against the value in the article, install it with rpm, check /usr/bin/cssd against the listed value and restart the component.
-
Plan the move to a supported Sophos Firewall
Sophos names this as the other remediation, because UTM is end of life. Sophos lists no workaround for the flaw.
-
Watch for changes
Check the Sophos advisory, the NVD record and the CISA catalogue again over the coming days. They may add exploitation details.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-118633 in Brandefense Atlas
The Atlas record of CVE-2026-118633: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-118633?
It is a path traversal flaw in Sophos UTM. Sophos says a remote attacker with no account can run commands as root after winning a race condition, when the email proxy is used with scanning enabled. Sophos rates it Critical.
Which Sophos UTM versions are affected?
Sophos lists Sophos UTM, all versions. The NVD record gives versions up to and including 9.724. Sophos Firewall is a different product and is not listed.
Is CVE-2026-118633 exploited?
Sophos' advisory does not say. CISA's Known Exploited Vulnerabilities catalogue, version 2026.10.28, does not list the CVE (checked 28 October 2026).
How do I fix CVE-2026-118633?
Update UTM to 9.724, then install the RPM patch from Sophos article KBA-000049692 and restart the component. Sophos also names a move to a supported Sophos Firewall as a remediation.
Is there a workaround?
No. The Sophos advisory lists the workaround as No. The two remediations it names are the manual patch and an upgrade to a supported Sophos Firewall.
Sources
- Resolved Pre-Auth RCE Vulnerability in Sophos UTM (CVE-2026-118633)Sophos
- Sophos UTM: RPM patch for an SMTP vulnerability (KBA-000049692)Sophos
- CVE-2026-118633NVD
- Sophos UTM: MyUTM status, Vulnerability disclosure and response to security incidentsSophos Community
- Known Exploited Vulnerabilities catalogCISA