Cisco Secure Email Gateway CVE-2026-76461 Critical SQL Injection Flaw Exploited in the Wild for Root Access
Cisco Secure Email Gateway is affected by CVE-2026-76461, a CVSS 9.8 critical vulnerability that is already being exploited in the wild. Attackers can obtain root privileges on the gateway simply by sending one specially crafted email, with no authentication, user interaction, or bypass required.
Attack Mechanics
The flaw is an SQL injection located in the mail parsing logic of AsyncOS. When the gateway processes incoming messages, insufficient input validation allows embedded malicious SQL statements to be executed as legitimate commands on the underlying operating system. The entire attack occurs during automated mail inspection, before any recipient opens the message.
Why the Impact Is Severe
Secure Email Gateway functions as the enterprise email boundary device, scanning all inbound and outbound traffic for malware and phishing. Once compromised with root access, an attacker can install persistent backdoors, monitor every message, intercept or alter business-critical emails, use the gateway as a pivot into the internal network, and send highly trusted internal phishing messages.
Affected Versions and Remediation
Impacted releases are 15.5 and earlier, 16.0, and 16.5. Cisco provides no mitigation steps and urges immediate upgrade to 16.5.0-780 (or the corresponding fixed builds 15.5.5-014 and 16.0.4-302). Cloud customers have been contacted directly by Cisco where malicious activity was detected, but should still verify their deployments.
Detection Guidance
Administrators should search mail_logs for suspicious SQL patterns such as COPY.*TO PROGRAM. Because root-level access allows log tampering, organizations must also review firewall and network device logs for unexpected outbound connections originating from the gateway and inspect any underlying virtualization platform for signs of further compromise.
Broader Context
This incident highlights the recurring risk posed by internet-facing security appliances that receive untrusted data yet run with elevated privileges. Security teams are advised to audit all perimeter devices for current firmware, unnecessary exposed services, and centralized logging to reduce similar exposure.
Related articles
Vulnerability Management in Atypical Environments: ICS, Networks, IoT, Mobile, Hardware, and ML Systems
Vulnerability management follows the same core process across environments—identify assets, scan, assess risk, prioritize, remediate, and verify—but each domain introduces critical constraints. In industrial control systems, scanning must avoid disrupting physical processes, requiring audit-mode authenticated scans, digital twins for testing, and strict change windows. Network devices frequently suffer from poor segmentation, default SNMP community strings, and exposed management interfaces that enable traffic redirection or configuration tampering. IoT ecosystems remain plagued by default credentials, as demonstrated by the Mirai botnet that took down major DNS infrastructure in 2016, while modern botnets like Reaper and VPNFilter exploit unpatched firmware at massive scale. Machine learning systems face novel threats including prompt injection, prompt leaking, and jailbreaking that can bypass safety controls or exfiltrate training data. Mobile platforms suffer from extreme fragmentation that prevents timely patching of vulnerabilities such as Stagefright, Pegasus, and BlueBorne. Hardware-level flaws like Spectre, Meltdown, and BadUSB demonstrate that even firmware and silicon require coordinated microcode, OS, and application updates.
Google Issues Chrome 153 Security Update Addressing 42 Vulnerabilities Including Three Critical Flaws
Google has released a major security update for its Chrome browser version 153, fixing a total of 42 vulnerabilities. The update includes three critical-severity issues that could allow attackers to execute arbitrary code or cause memory corruption. Patches are now available for Windows, macOS, and Linux platforms, with versions 153.0.8010.48 and 153.0.8010.47. Among the critical fixes are out-of-bounds read in WebGL, use-after-free in Internals, and another use-after-free in Workers. The release also resolves 28 high-severity flaws affecting the V8 JavaScript engine, ServiceWorker, Skia, DOM, PDF, and other components. Medium and low severity issues were addressed as well, bringing the total to 42 vulnerabilities resolved.
Oracle Releases September 2026 Critical Security Patch Update Fixing 673 Issues Across Multiple Products
Oracle has published its monthly Critical Security Patch Update (CSPU) on September 15, 2026, delivering a total of 673 security fixes. The update addresses 672 unique CVEs after removing duplicates and targets a wide range of products including Oracle Database Server, Oracle Fusion Middleware, Oracle E-Business Suite, PeopleSoft, Siebel, and Oracle VM VirtualBox. Of the fixes, 607 received a CVSSv3 base score of 7.0 or higher, with 104 scoring 9.0 or above. Six vulnerabilities carry the maximum score of 10.0, while 15 are rated 9.9 and 44 are rated 9.8. Additionally, 247 of the issues can be exploited remotely without authentication. The CSPU serves as a smaller, more frequent complement to Oracle’s quarterly Critical Patch Update (CPU) releases.
How Modern API Attacks Abuse Legitimate Functionality Instead of Exploiting Vulnerabilities
Traditional API incidents once centered on authorization errors, access control issues, SQL injections, and known vulnerability exploitation. Today, many attacks on APIs no longer require finding code flaws; attackers simply use documented methods, valid authorization, and correct parameters at unexpected scale or timing. NGENIX security teams observe three main behavioral patterns: Burst attacks that overload resource-heavy endpoints, Shortwave attacks that exploit race conditions through timed parallel requests, and Carpet Bombing that distributes activity across dozens of endpoints for reconnaissance or scalping. These techniques often bypass WAF because each individual request appears fully compliant with API specifications. Protection is shifting toward behavioral analysis, sliding-window rate limiting, and monitoring of overall client behavior rather than single-request signatures. Real-world cases include sudden catalog scraping during contests and mass reservation of airline seats without purchases, leading to degraded service for legitimate users.