How to fix CVE-2026-76519: Cisco Secure Email Gateway (exploited in the wild)

A vulnerability in the Advanced Malware Protection (AMP) feature of Cisco Secure Email Gateway could allow an unauthenticated, remote attacker to write arbitrary files on the underlying operating system. This vulnerability is due to improper handling of email attachments when the file reputation service is enabled. An attacker could exploit this vulnerability by sending an email that contains a crafted attachment through an affected device. A successful exploit could allow the attacker to write arbitrary files and execute commands with root privileges on the underlying operating system.

• Severity: CRITICAL (CVSS 3.1 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
• Weakness: CWE-23.
• NVD published 2026-10-14, status Analyzed.

Anyone running Cisco Secure Email Gateway in the version ranges below. Internet-facing instances are the priority.

• cisco asyncos: from 15.0 up to (not including) 15.5.5-014.
• cisco asyncos: from 16.0 up to (not including) 16.5.0-780.

Version ranges come from the NVD CPE configuration. Confirm against the vendor advisory before you rely on them.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-10-14; federal remediation due date 2026-10-17.

• EPSS (probability of exploitation activity in the next 30 days): 1.57%, higher than 75% of all scored CVEs (as of 2026-10-24).
• CVERadar threat level: 64/100 (see methodology).
• Likely ATT&CK techniques: T1190 Exploit Public-Facing Application (inferred); T1083 File and Directory Discovery (inferred).

1. Find every instance. List where Cisco Secure Email Gateway runs, including test, DR and forgotten internet-facing systems, and record the installed version.

   show version

2. Upgrade to a fixed release. cisco asyncos: 15.5.5-014 or later; cisco asyncos: 16.5.0-780 or later. Get the build from the vendor advisory.
3. If you can't patch today, follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
4. Verify the fix. Re-run the version check above on every instance and confirm it reports the fixed build (15.5.5-014 or later). Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• T1190 Exploit Public-Facing Application: Review WAF, reverse-proxy and application logs for unusual requests to Secure Email Gateway (odd paths, oversized or encoded payloads, bursts of errors), going back to at least 2026-10-14.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-76519 nvd.nist.gov/vuln/detail/CVE-2026-76519
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-76519
• Vendor link from CISA KEV sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (2026-10-24) api.first.org/data/v1/epss?cve=CVE-2026-76519