The email security gateway is usually filed under "email", next to spam filters and phishing training. In autumn 2026 attackers treated it as what it really is: an internet-facing appliance that sits in the path of every message, runs as root and is rarely watched. Between 14 September and 10 November 2026, CISA added five exploited vulnerabilities in three vendors' email gateways to its Known Exploited Vulnerabilities (KEV) catalog: two in Cisco Secure Email Gateway, one in Fortinet FortiMail and two, chained together, in Barracuda Email Security Gateway. This article reconstructs the sequence from the vendor advisories, explains why mail gateways are worth so much to an attacker and gives you a checklist for the days after the patch. It belongs to our analysis of 250 KEV entries from March to November 2026, where one entry in four was a network edge device.
Key Takeaways
- Three vendors, five KEV entries, under two months. Cisco Secure Email Gateway (14 September and 14 October), FortiMail (1 October) and Barracuda ESG (10 November).
- Both Cisco flaws are triggered by an email. No management interface needs to be exposed: a crafted message or attachment passing through the gateway is enough.
- FortiMail and Barracuda were reachable through web interfaces (the FortiMail webmail and IBE service, the Barracuda administrative UI) that should rarely face the internet.
- All five entries carry CISA's forensic triage flag. Patching closes the flaw; it does not tell you whether the appliance was already compromised.
- SPF, DKIM and DMARC still matter, but they protect your domain's name, not the box that filters your mail. You need both.
The Sequence: Four Advisories, Five CVEs
| Vendor and product | CVE | Added to KEV | How it is reached | Impact per the vendor |
|---|---|---|---|---|
| Cisco Secure Email Gateway | CVE-2026-76461 | 14 September 2026 | A crafted email processed by the gateway, regardless of configuration | SQL injection leading to commands as root |
| Fortinet FortiMail | CVE-2026-104286 | 1 October 2026 | Crafted HTTP or HTTPS requests, unauthenticated | Arbitrary file write on the system, which can lead to code execution |
| Cisco Secure Email Gateway | CVE-2026-76519 | 14 October 2026 | A crafted attachment, when File Reputation is enabled and Content Scanner Tools is older than 25.3.0.5525 | Arbitrary file write leading to commands as root |
| Barracuda Email Security Gateway | CVE-2026-116606 | 10 November 2026 | The administrative UI, when reachable by the attacker | Authentication bypass that can restore a crafted configuration backup |
| Barracuda ESG and other Barracuda appliances | CVE-2026-111560 | 10 November 2026 | Administrative access (obtained through the previous flaw) | OS command injection with root privileges |
Sources: CISA KEV catalog (version 2026.11.10) and the vendor advisories linked below.
Cisco Secure Email Gateway, September and October
Cisco published the first advisory on 14 September 2026 (cisco-sa-esa-inj-2bLVGmhX). CVE-2026-76461 is a SQL injection in the email parsing logic of AsyncOS, rated CVSS 9.8. An unauthenticated attacker sends an email containing malicious SQL statements; the gateway processes it and the attacker can run commands as root. Cisco states that physical and virtual appliances are affected regardless of device configuration, that there are no workarounds, and that it became aware of active exploitation in September 2026 during a support case. The fixed releases are 15.5.5-014 (with an updated fix released on 31 October, which you confirm with retroscannerstatus and a Retro Remediation Engine version of 4.0.2 or later), 16.0.4-302 and 16.5.0-780, the release Cisco recommends for everyone earlier than 16.5.
A month later, on 14 October, came CVE-2026-76519 (cisco-sa-esa-afw-zqYJkjxp), also CVSS 9.8. This time the vehicle is an attachment: improper handling lets an attacker write arbitrary files and then execute commands as root. It requires the File Reputation service to be enabled and assigned to a mail policy, and Content Scanner Tools older than 25.3.0.5525. Cisco again reported active exploitation and no workarounds. Content Scanner Tools 25.3.0.5525 or later contains the fix and can be updated without a software upgrade or a restart.
The detail that matters: neither Cisco flaw needs an exposed administrative interface. The attack arrives on port 25, the one port a mail gateway must leave open. Restricting management access, good practice as it is, did not help here. Only the update did.
FortiMail, October
Fortinet published FG-IR-26-175 on 1 October 2026, the same day CISA added CVE-2026-104286 to KEV. It is a path traversal combined with improper handling of NULL bytes, rated CVSS 9.8, that lets an unauthenticated attacker write arbitrary files through crafted HTTP or HTTPS requests. Fortinet states that it has been reported as exploited in the wild. Affected branches are 8.0 (up to 8.0.1, fixed in 8.0.2), 7.6 (up to 7.6.6, fixed in 7.6.7), 7.4 (up to 7.4.8, fixed in 7.4.9), 7.2 (up to 7.2.9, fixed in 7.2.10, which the advisory listed as upcoming) and every 7.0 release, which must migrate to a fixed branch. FortiMail Cloud was remediated by Fortinet on 5 October.
The advisory lists workarounds that tell you where the attack enters: disable the IBE (identity-based encryption) service, restrict access to the FortiMail webmail interface from the internet, or, if a WAF sits in front, block POST requests to /ibe that contain ../. It also lists indicators to look for: a cron job running a command under /migadmin, an unexpected "archive account" added from the CLI with a remote host and the remote directory /uploads, and IBE decrypter errors in the encryption logs.
Barracuda ESG, November
Barracuda published its advisory on 2 November 2026 (trust.barracuda.com) and updated it on 5 and 9 November. Two CVEs work together. CVE-2026-116606 (CVSS 9.3) is a pre-authentication authorisation bypass on the Email Security Gateway; Barracuda specifies that exploitation requires the administrative UI to be reachable by the attacker. According to the KEV description and Mandiant's disclosure MNDT-2026-0042, it lets the attacker invoke the configuration-import function and restore a crafted backup, changing the appliance's global configuration. CVE-2026-111560 (CVSS 8.6) is a command injection that requires administrative access and runs commands as root through a crafted time zone value; it affects ESG and also Barracuda's Load Balancer ADC, Web Application Firewall, Message Archiver, WAF Control Center and Web Security Gateway. Chained, the two give an unauthenticated attacker root access.
In its 9 November update Barracuda said it had observed exploitation activity affecting a small number of organisations. CISA added both CVEs to KEV on 10 November with a due date of 13 November. Barracuda's patches are BNSF-40425 for ESG 9.4.017 and later and BNSF-40430 for earlier versions. Barracuda asks customers to check that the patch was applied (automatic patching may not have reached every appliance, and devices several versions behind may need several updates) and to restrict administrative interfaces to trusted internal networks.
Why Mail Gateways Are Worth So Much to an Attacker
- They are inline. Every inbound and often every outbound message passes through them. Whoever controls the gateway can read, copy, alter or quietly forward mail, including invoices, contracts and password reset links.
- They hold credentials. Gateways commonly connect to the directory to validate recipients and to authenticate users to quarantine or webmail portals. A compromised appliance can expose those accounts.
- They are trusted. Downstream mail servers accept what the gateway passes. An attacker inside it can deliver messages that bypass the filtering that was supposed to stop them.
- They are hard to watch. You cannot install an endpoint agent on a vendor appliance. Unless its logs are collected and read somewhere else, a compromise can last for weeks.
- They must face the internet. Port 25 has to stay open to receive mail. As the Cisco cases show, that one port can be enough.
Step 1: Check Your Exposure
Before you patch, find out exactly what you have and what the internet can see.
- Inventory. List every mail security appliance, physical, virtual or hosted, with model, software version and, for Cisco, the Content Scanner Tools version and whether File Reputation is enabled. Include secondary or disaster recovery appliances and clustered members: Cisco recommends checking every device in a cluster.
- Look from outside. From an external network, check which ports and services each appliance exposes. SMTP (25) is expected. The administrative interface, webmail, quarantine portals and services such as FortiMail IBE should be exposed only if there is a documented business reason.
- Read your MX records. They tell you, and anyone else, which product filters your mail. Attackers use the same records to choose targets.
- Do not forget cloud versions. Cisco and Fortinet both state that their cloud-hosted email services were updated by the vendor. Confirm with your provider rather than assuming.
Step 2: Patch, Then Check for Compromise
CISA flagged all five entries for forensic triage, which under its June 2026 directive means federal agencies must not only fix the flaw but also determine whether the appliance was compromised. For a European company there is no directive, but the logic is the same: a gateway exploited before the update stays compromised after it.
- Cisco: search the mail logs on every appliance for suspicious SQL statements (Cisco's example is
grep -i "COPY.*TO PROGRAM"), cross-check network and firewall logs for unexpected uploads to or downloads from external addresses, and remember that SSH keys shared between cluster members may be exposed: Cisco recommends restoring every member of a cluster that contains a compromised appliance. - FortiMail: look for the indicators in FG-IR-26-175: unexpected cron jobs under
/migadmin, archive accounts pointing to a remote host, unexplained admin logouts and IBE decrypter errors. - Barracuda: since CVE-2026-116606 restores a crafted configuration, compare the current configuration against a known-good backup. Look for changes you did not make: new administrators, altered routing or relay rules, new forwarding, changed LDAP or authentication settings, a modified time zone value.
- Everyone: rotate the secrets the appliance held, including directory bind accounts, administrator passwords, API keys and certificates. If you find evidence of compromise, treat it as an incident, preserve the logs and involve your incident response plan. Our article on why patched is not the same as clean covers the method in more depth.
Step 3: Email Authentication Still Matters
None of these CVEs is about SPF, DKIM or DMARC. Those records protect your domain's name: they decide whether someone else can send email that appears to come from you. They are still worth fixing in the same pass, for two reasons. First, an attacker who has read your mail flow through a compromised gateway has everything needed to impersonate you convincingly; a DMARC policy of p=none lets those messages reach your customers. Second, a gateway rebuild or replacement is the moment SPF records go out of date. Check that SPF lists only the senders you use, that DKIM signs outbound mail, and that DMARC has moved to quarantine or reject once your reports show legitimate mail passing. Our phishing protection guide explains the full setup.
Step 4: Detection Over Time
A gateway is an appliance you cannot instrument, so you watch it from outside and through its logs. Send its system, admin and mail logs to a central platform; alert on new administrator accounts, configuration imports, unexpected outbound connections from the appliance and admin logins from unusual addresses. If no one in the company reads those alerts at night or at weekends, that is the gap a managed SOC fills.
Checklist for IT Managers
- List every email security appliance, its version and its exposed services.
- Confirm the fixed release is installed: Cisco 16.5.0-780 or another fixed release plus Content Scanner Tools 25.3.0.5525 or later; FortiMail 8.0.2, 7.6.7, 7.4.9 or 7.2.10; Barracuda patches BNSF-40425 or BNSF-40430.
- Remove administrative interfaces, webmail and IBE from the internet unless there is a documented need.
- Run the vendor's compromise checks and compare configurations with a known-good backup.
- Rotate credentials, keys and certificates stored on the appliance.
- Check SPF, DKIM and DMARC, and move DMARC towards enforcement.
- Send gateway logs to a monitored platform and define alerts.
How Orizon Helps
RECON External starts from your domain name, maps the hosts and services you expose (mail gateways, webmail and admin panels included), matches the detected products to known CVEs weighed by CISA KEV, Exploit-DB, Metasploit and EPSS, and then verifies each finding: Proven, To verify or Closed, with the evidence of every test. It also reads your SPF, DKIM and DMARC records and says what each one allows, for example when a DMARC policy does not block spoofing. For the watching part, Oversight is our 24/7 managed SOC on the CYREBRO platform: analysts on duty around the clock validate every detection, and Orizon intervenes when it matters.