Cisco Secure Email Gateway AMP flaw exploited in the wild, allows unauthenticated root command execution
Cisco has fixed CVE-2026-76519, a critical and actively exploited flaw in the AMP feature of Secure Email Gateway that lets an unauthenticated attacker run commands as root. CERT-EU urges organisations running these appliances to patch immediately and check them for signs of compromise.
What to do now
- Product
- Cisco Secure Email Gateway (AsyncOS)
- Affected versions
- AsyncOS 15.5 before 15.5.5-014, 16.0, 16.5 before 16.5.0-780, with File Reputation enabled and Content Scanner Tools earlier than 25.3.0.5525
- Fixed in
- AsyncOS 15.5.5-014, 16.5.0-780; Content Scanner Tools 25.3.0.5525 and later
- CVE
- CVE-2026-76519
On 14 October 2026 Cisco released an advisory for a critical vulnerability in the Advanced Malware Protection (AMP) feature of Cisco Secure Email Gateway. CERT-EU relayed the warning the following day. Cisco's PSIRT says it is aware of active exploitation.
Tracked as CVE-2026-76519, the bug is a relative path traversal flaw. It stems from improper handling of email attachments when the File Reputation service is enabled. An attacker only has to send an email carrying a crafted attachment through the device, and no authentication is required. A successful exploit lets the attacker write arbitrary files and execute commands with root privileges on the underlying operating system.
Affected systems are physical and virtual appliances running AsyncOS 15.5 before 15.5.5-014, all 16.0 releases, and 16.5 before 16.5.0-780. Two conditions must also be met: File Reputation is enabled and assigned to a mail policy, and Content Scanner Tools is older than 25.3.0.5525. The fix also reaches every licensed and supported AsyncOS release through Content Scanner Tools 25.3.0.5525 or later. Secure Email and Web Manager and Secure Web Appliance are not affected. Cisco says Secure Email Cloud Gateway customers need to take no action, because a fixed scanner version is already deployed.
Clustered deployments need particular attention. Cisco warns that the private SSH keys used between cluster members can be read on a compromised appliance, which could let an attacker move on to the other nodes. With root access, an attacker can also delete or hide evidence of exploitation.
To check an appliance, Cisco suggests running grep "System Security" system_logs. The message "Suspected compromise indicator was found" means a compromise was detected. "Security scan did not complete" means a compromise is suspected and the Cisco TAC should be contacted. CERT-EU notes that Cisco has not published any concrete indicators of compromise and that it is unclear how these log messages are produced. Cisco therefore advises cross-checking against network and firewall logs collected outside the appliance.
To see whether File Reputation is on, open the web interface and go to Mail Policies, then Incoming or Outgoing Mail Policies, then Advanced Malware Protection. The CLI command contentscannerstatus shows the installed Content Scanner Tools version.
What to do now
- Update Content Scanner Tools to 25.3.0.5525 or later, or upgrade AsyncOS to 15.5.5-014 or 16.5.0-780, starting with internet-facing appliances.
- Confirm exposure by running contentscannerstatus and checking whether File Reputation is enabled in your AMP mail policies.
- Run grep "System Security" system_logs on each appliance and trigger your incident response plan if a compromise is detected or suspected.
- Review network and firewall logs outside the appliance for unexpected uploads to, or downloads from, external IP addresses.
- If a clustered appliance is compromised, treat the other cluster members as potentially affected, since shared SSH keys may have been exposed.