Exploited now
Remediation guideCVE-2026-76461
Cisco Secure Email Gateway SQL Injection Vulnerability
- CISA KEV
- Known exploitedadded 14 Sep 2026; US federal deadline 17 Sep 2026
- Exploit likelihood
- 40%99th 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 email parsing of Cisco AsyncOS Software for Cisco Secure Email Gateway could let a remote attacker who hasn't logged in run arbitrary commands with root privileges on the appliance's operating system.
It comes from insufficient validation in the email parsing logic; the attack arrives as email through the device.
Because the attack comes in as email, restricting access to the management interface alone isn't a substitute for upgrading. our analysis
Cisco became aware of active exploitation in September 2026, and CISA lists it as known to be exploited.
2Am I affected?
It affects Cisco Secure Email Gateway, physical and virtual, regardless of device configuration.
Cisco has confirmed it does not affect Secure Email and Web Manager or Secure Web Appliance.
Cisco's fix tables list release trains with the first release that includes the fix. The 15.5 and earlier row covers the older trains in Cisco's affected list (13.0 to 15.0).
Affected releases are summarised by release train in the Fix table.
Check your version
A command to show the running AsyncOS release: Not stated by vendor.
3Fix
If you suspect compromise on a virtual appliance, Cisco says to maintain forensic information as your incident-handling policy requires, and record it before any recovery step: deploying a new instance will destroy the configurations and logs. On a physical appliance, Cisco recommends contacting TAC (see Was I hit?).
So if there's any chance the appliance was compromised, preserve forensic information and run the log check under Was I hit? before you upgrade or rebuild. our analysis
Cisco strongly recommends that customers running releases earlier than 16.5 migrate to 16.5.0-780.
In the web-based management interface: System Administration > System Upgrade, Upgrade Options, Download and Install, choose a release, choose the Upgrade Preparation options, then Proceed. At the CLI: run upgrade, enter DOWNLOADINSTALL, choose a release and the appropriate options. Either way the device reboots when the upgrade is complete.
Cisco has already upgraded all Cisco Secure Email Cloud devices to 16.5.0-780.
| Product | Release | First fixed release |
|---|---|---|
| Cisco AsyncOS for Cisco Secure Email Gateway Software | 15.5 and earlier | 15.5.5-014 |
| 16.0 | 16.0.4-302 | |
| 16.5 | 16.5.0-780 |
4Can't patch tonight?
There are no workarounds that address this vulnerability.
5Was I hit?
To check for attempted exploitation, Cisco says to review the mail_logs for suspicious SQL statements, on each device of a cluster. Its non-exhaustive example, run at the appliance CLI against the mail logs (named mail_logs by default):
> grep -i "COPY.*TO PROGRAM" mail_logs
Replace mail_logs if your mail log subscription has a different name. our analysis
Any entry in the output may indicate malicious activity.
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.
Because of this, an empty result from the log check doesn't prove the device wasn't compromised. our analysis
If you suspect compromise: on a physical appliance, Cisco recommends contacting TAC, with remote access enabled on the appliance to speed up the investigation. On a virtual appliance, Cisco strongly recommends, when possible, recording forensic information first, then deploying a new VM on a fixed release, rebuilding the product configuration, renewing credentials and cryptographic material, and monitoring. If you can't restore the appliance, contact TAC.
Clusters: a compromised member's private SSH keys could be accessed and used to compromise the other members, so Cisco strongly recommends restoring every member of a cluster that contains at least one compromised appliance.
If exploitation isn't suspected and the device runs an affected release, Cisco strongly recommends upgrading to a fixed release.
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. If Cisco contacted you, it strongly recommends renewing credentials and any cryptographic material installed on the appliance, when possible. For all Secure Email Cloud customers, Cisco strongly recommends restricting access to the appliance and implementing robust access control mechanisms.
6Sources
- Cisco Secure Email Gateway SQL Injection VulnerabilityCisco · primary source
- Known Exploited Vulnerabilities catalog: CVE-2026-76461CISA
- CVE-2026-76461NVD
- Exploit Prediction Scoring System (EPSS)FIRST · exploit likelihood, updated daily
Summary of public vendor guidance. Verify against the vendor advisory before acting.
See CVE-2026-76461 in the exploited-now list (exploit likelihood, CISA's description, deadline).
More Cisco guides
- CVE-2026-20079Cisco FMC authentication bypass
- CVE-2026-20349Cisco ASA/FTD SSL VPN denial of service (HTTP requests)
- CVE-2026-76418Cisco ASA/FTD SSL VPN denial of service (secondary authentication)
- CVE-2026-76460Cisco ISE authentication bypass
- CVE-2026-76504Cisco SD-WAN Manager API authentication bypass
- CVE-2026-76519Cisco Secure Email Gateway file write (AMP)