NETWORK INCIDENTS

Exploited now

Remediation guide
Cisco · Secure Email Gateway

CVE-2026-76519

Cisco Secure Email Gateway Arbitrary File Write Vulnerability

CISA KEV
Known exploitedadded 14 Oct 2026; US federal deadline 17 Oct 2026
Exploit likelihood
6.2%94th percentile · FIRST EPSS, 2026-11-15
Severity
9.8 CriticalCVSS 3.1, Cisco
Last verified
30 Oct 2026against the sources below

1In plain language

A flaw in the Advanced Malware Protection (AMP) feature of Cisco Secure Email Gateway could let an attacker on the network, without logging in, write arbitrary files on the appliance's operating system and run commands with root privileges.

It comes from improper handling of email attachments when the file reputation service is enabled.

Cisco became aware of active exploitation in October 2026, and CISA lists it as known to be exploited.

2Am I affected?

It affects Cisco Secure Email Gateway, physical and virtual, running a vulnerable release of Cisco AsyncOS Software, when both conditions are met: the File Reputation service (part of Cisco AMP) is enabled and assigned to a mail policy, and the Content Scanner Tools version is earlier than 25.3.0.5525.

Cisco has confirmed it does not affect Secure Email and Web Manager or Secure Web Appliance.

Affected releases are summarised by release train in the Fix table.

Check your version

File Reputation: in the web-based management interface, choose Mail Policies > Incoming Mail Policies > Advanced Malware Protection, or Mail Policies > Outgoing Mail Policies > Advanced Malware Protection. Choose a mail policy and look at the Enable File Reputation check box: if it's checked, file reputation is enabled.

Check each incoming and outgoing mail policy, not just one. our analysis

Content Scanner Tools version: run contentscannerstatus at the CLI. A version earlier than 25.3.0.5525 is a vulnerable version; Cisco's example shows Content Scanner Tools 25.2.0.5427.15.5.001. The appliance is affected only if File Reputation is also enabled and assigned to a mail policy.

> contentscannerstatus

In the output, look at the Content Scanner Tools line.

A command to show the running AsyncOS release: Not stated by vendor.

3Fix

Cisco warns that upgrading a compromised instance will destroy forensic data and logs.

So if there's any chance the appliance was compromised, run the log check under Was I hit? and record forensic information before upgrading. our analysis

Cisco's record also lists releases in the 13.0, 13.5, 14.0, 14.2, 14.3 and 15.0 trains (builds 13.0.0-392 to 15.0.5-016) as affected; they have no row in the fix table. Cisco strongly recommends that releases earlier than 16.5 migrate to 16.5.0-780. The Content Scanner Tools update below reaches licensed and supported releases.

Cisco strongly recommends that customers running AsyncOS releases earlier than 16.5 migrate to 16.5.0-780.

The fix also reaches every licensed and supported AsyncOS release through an updated Content Scanner Tools package: versions 25.3.0.5525 and later contain it. Updating Content Scanner Tools needs no software upgrade or restart, and customers with automatic updates enabled don't need to do anything once the update is applied.

To update Content Scanner Tools by hand, run contentscannerupdate at the CLI, then run contentscannerstatus to confirm the version. Customers who have disabled automatic updates should apply the update manually.

Cisco Secure Email Cloud Gateway customers don't need to apply the fix: a fixed Content Scanner Tools version is already deployed. If Cisco has contacted you about your Secure Email Cloud devices, Cisco strongly recommends renewing credentials and any cryptographic materials installed on the appliance, when possible. For all Secure Email Cloud customers, Cisco also strongly recommends restricting access to the appliance and implementing robust access control mechanisms.

ProductReleaseFirst fixed release
Cisco AsyncOS Software for Cisco Secure Email Gateway15.515.5.5-014
16.0Migrate to a fixed release.
16.516.5.0-780

4Can't patch tonight?

There are no workarounds that address this vulnerability.

Cisco's general hardening advice: upgrade to the latest AsyncOS; prevent access from the internet to the appliance, or if it's needed, restrict access to known, trusted hosts on the ports and protocols in the user guides; and separate mail and management functions onto different network interfaces.

Cisco doesn't present this as a mitigation for this vulnerability: there are no workarounds, and upgrading or updating Content Scanner Tools is the fix. our analysis

5Was I hit?

To check for attempted exploitation, Cisco says to review the system_logs with the command below. If the device is in a cluster, review the logs of each cluster device.

> grep "System Security" system_logs

In the output, look at the System Security: line.

"Suspected compromise indicator was found" means compromise detected: follow the Recommendations section of the advisory. "Security scan did not complete" means contact Cisco TAC. "No compromise indicator was found" means no compromise detected: upgrade to a fixed release if applicable.

Attackers with root access may remove or hide evidence, so Cisco strongly recommends also checking network and firewall logs outside the device, for example for unexpected uploads from the device to external IP addresses or downloads from malicious IP addresses.

If you suspect compromise: on a physical appliance, Cisco recommends contacting TAC. On a virtual appliance, record forensic information first (upgrading a compromised instance destroys forensic data and logs), then deploy a new VM on a fixed release, rebuild the configuration without importing old configuration files, renew credentials and cryptographic material, and keep monitoring. If you can't restore the appliance, Cisco recommends contacting TAC.

Clusters: private SSH keys used between cluster members could be accessed on a compromised appliance and used against the other members, so Cisco strongly recommends restoring every member of a cluster that contains a compromised appliance.

On Cisco Secure Email Cloud, administrators without CLI access may not be able to run this check themselves. Cisco has directly contacted customers whose devices showed malicious activity.

What it means if none of the three System Security messages appear: Not stated by vendor.

6Sources

Summary of public vendor guidance. Verify against the vendor advisory before acting.

See CVE-2026-76519 in the exploited-now list (exploit likelihood, CISA's description, deadline).

More Cisco guides