cisco-sa-esa-inj-2bLVGmhXCriticalCVSS 9.8

Cisco Secure Email Gateway SQL Injection Vulnerability

Published
September 14, 2026
Last Modified
November 3, 2026

🔗 CVE IDs covered (1)

CVE-2026-76461 →

📋 Description

A vulnerability in the email parsing of Cisco AsyncOS Software for Cisco Secure Email Gateway could allow an unauthenticated, remote attacker to execute arbitrary commands with root privileges on the underlying operating system.

This vulnerability is due to insufficient validation in the email parsing logic. An attacker could exploit this vulnerability by sending a crafted email message that contains malicious SQL statements through an affected device. A successful exploit could allow the attacker to execute arbitrary SQL statements, leading to command execution with root privileges on the underlying operating system.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

CVE-2026-76461 — Cisco Secure Email Gateway SQL Injection Vulnerability (CVSS 3.1 9.8, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)

🎯 Affected products24

  • Cisco Secure Email
  • Cisco Secure Email 13.0.0-392
  • Cisco Secure Email 13.0.5-007
  • Cisco Secure Email 13.5.1-277
  • Cisco Secure Email 13.5.4-038
  • Cisco Secure Email 14.0.0-698
  • Cisco Secure Email 14.2.0-620
  • Cisco Secure Email 14.2.1-020
  • Cisco Secure Email 14.3.0-032
  • Cisco Secure Email 15.0.0-104
  • Cisco Secure Email 15.0.1-030
  • Cisco Secure Email 15.0.3-002
  • Cisco Secure Email 15.0.5-016
  • Cisco Secure Email 15.5.0-048
  • Cisco Secure Email 15.5.1-055
  • Cisco Secure Email 15.5.2-018
  • Cisco Secure Email 15.5.3-022
  • Cisco Secure Email 15.5.4-012
  • Cisco Secure Email 16.0.0-050
  • Cisco Secure Email 16.0.0-054
  • Cisco Secure Email 16.0.1-017
  • Cisco Secure Email 16.0.2-112
  • Cisco Secure Email 16.0.3-044
  • Cisco Secure Email 16.0.4-016

✅ Remediation

Cisco has released software updates that address this vulnerability. https://software.cisco.com Workarounds: There are no workarounds that address this vulnerability.

🔗 References (11)