The short version
- The flaw. CVE-2026-76519 is a path traversal weakness in the Advanced Malware Protection feature of Cisco Secure Email Gateway, caused by how email attachments are handled. A successful exploit lets an unauthenticated remote attacker write arbitrary files and run commands with root privileges. It is scored 9.8 out of 10.
- Exploitation. Cisco says it became aware of active exploitation in October 2026 and published indicators of compromise. It has not said how many devices were attacked, who is responsible, or whether any attacker gained root.
- Who is exposed. Only gateways with the File Reputation service enabled and assigned to a mail policy, and Content Scanner Tools older than 25.3.0.5525, are vulnerable. Secure Email and Web Manager and Secure Web Appliance are not affected.
- Fixes and cloud customers. Cisco shipped the underlying fix on 14 September in a hardening release and now offers a scanner update that installs without a restart. Cisco has contacted owners of Secure Email Cloud devices showing indicators of possible compromise and says it has already applied mitigations on its cloud instances.
Timeline
| Date | Event |
|---|---|
| 14 September | Cisco issues a hardening release, including AsyncOS builds 15.5.5-014 and 16.5.0-780, that carries the fix for the file-write flaw under a grouped CVE, and discloses a separate SQL injection flaw, CVE-2026-76461, also exploited. |
| October | Cisco's product security team learns that CVE-2026-76519 is being exploited, according to the company. |
| 14 October | Cisco publishes a dedicated advisory for CVE-2026-76519 with compromise indicators, and CISA adds the flaw to its Known Exploited Vulnerabilities catalogue. |
How the attack works
The weakness sits in the part of Secure Email Gateway that inspects attachments, the Advanced Malware Protection feature. By sending an email carrying a specially crafted attachment through an unpatched appliance, an attacker with no credentials can write files to the underlying operating system and then execute commands as root. Cisco found the bug through its own internal security scanning and issued a dedicated advisory after confirming that it was being used.
Cisco says it learned of the attacks in October 2026. It has published log messages that administrators can use to hunt for intrusions, but warns that an attacker who has obtained root could delete or conceal evidence. The advisory does not say what the compromise scan looks for.
This is the second Secure Email Gateway flaw Cisco has confirmed under attack within a month. The first, CVE-2026-76461, is a SQL injection weakness in the gateway's email parsing that was disclosed on 14 September and added to the CISA catalogue the same day. The two sit in different parts of the software and need different log checks, and Cisco has not linked the attacks.
Who is affected
Two conditions must both be met: the File Reputation service must be enabled and assigned to a mail policy, and the installed Content Scanner Tools must be older than 25.3.0.5525. Both physical and virtual gateways on vulnerable AsyncOS releases are exposed. Secure Email and Web Manager and Secure Web Appliance are not affected.
Cisco has contacted operators of its managed Secure Email Cloud service where it found indicators of possible compromise, and says it is handling remediation and recovery. It has already deployed the fixed scanner there, so those customers need no action to receive the fix. The Shadowserver internet security watchdog tracks nearly 300 Secure Email Gateway instances exposed online, though it does not say how many are decoys or have since been secured.
Detection and recovery
Cisco's published check is a single command on the appliance that searches the system logs for entries beginning "System Security" and returns one of three messages: a suspected compromise indicator was found, the security scan did not complete, or no indicator was found. It should be run on every member of a cluster. A clean result is not proof of safety, so Cisco also asks administrators to review firewall and network logs held outside the device for unexpected uploads to, or downloads from, external addresses.
There is no workaround. For a virtual appliance that shows signs of compromise, Cisco's guidance is to preserve forensic data first, because upgrading a compromised instance destroys its logs, then build a new virtual machine on a fixed release and rebuild the configuration without importing any earlier configuration file. Credentials and cryptographic material must be renewed, and every member of a cluster containing a compromised appliance should be restored, since cluster members authenticate to each other with SSH key pairs. Owners of affected physical appliances are asked to contact Cisco's Technical Assistance Center.
What is not known yet
- Who is carrying out the attacks and what they are after.
- How many gateways have been attacked, and whether any attacker obtained root on a device.
- How long exploitation went on before Cisco became aware of it in October.
- Whether the two Secure Email Gateway flaws exploited within a month are the work of the same actor.
- Which AsyncOS releases Cisco counts as licensed and supported for the scanner-only update.
What to do
If you run Cisco Secure Email Gateway
- Run contentscannerstatus on every gateway and every cluster member and confirm Content Scanner Tools is 25.3.0.5525 or later.
- Where automatic scanner updates are off, run contentscannerupdate or enable updates under Security Services > Service Updates.
- Move gateways to a fixed AsyncOS release listed in Cisco's advisory; there is no workaround.
- Search the system logs for "System Security" entries and cross-check firewall and network logs for unexpected transfers to or from external addresses.
If a gateway shows signs of compromise
- Preserve logs and other evidence before changing anything, because an upgrade destroys forensic data.
- On a virtual appliance, deploy a new virtual machine on a fixed release and rebuild the configuration from scratch rather than importing the old one.
- Renew credentials and cryptographic material, and restore every member of a cluster that contains a compromised appliance.
- For a physical appliance, contact Cisco's Technical Assistance Center and enable remote access for its engineers.
For everyone else
- Treat email security appliances as high-value internet-facing systems and keep the components that scan attachments in the same patch cycle as the rest of the estate.
- When a vendor says a fix arrives as a background component update, verify the installed version rather than assuming it applied.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.