OFFSEC · Offensive Security

Cisco’s email gateway hardening bundle now holds two exploited bugs, and one patch train misses the second

CVE-2026-76519, a root-level file write delivered by email attachment, was fixed a month ago inside a class-level CVE. Estates on AsyncOS 16.0 that patched for September's exploited SQL injection are not covered for it.

The finding

Cisco has split a second actively exploited vulnerability out of its September hardening release for Secure Email Gateway [1][2]. CVE-2026-76519, published on 14 October, is a relative path traversal in the file reputation component of Advanced Malware Protection. An unauthenticated sender can write arbitrary files to the appliance operating system with a crafted attachment and execute commands as root [1]. It scores 9.8. There is no workaround [1].

The fix is a month old. On 14 September Cisco’s hardening release grouped internally found flaws into one CVE per weakness class. The path traversal class was CVE-2026-76440, rated 9.8 [2][13]. That advisory now carries two footnotes. One vulnerability in the CWE-23 path traversal class is actively exploited. So is one in the CWE-707 injection class [2]. The second is CVE-2026-76461, an SQL injection in email parsing that was disclosed and exploited in September [3][9]. CISA gave federal agencies until 17 September to fix that one [12].

“In October 2026, the Cisco PSIRT became aware of active exploitation of this vulnerability.” — Cisco, advisory cisco-sa-esa-afw-zqYJkjxp, 14 October 2026 [1]

What the advisories state

  • Exposure requires File Reputation enabled and assigned to a mail policy, and Content Scanner Tools older than 25.3.0.5525. Secure Email and Web Manager and Secure Web Appliance are not affected [1].
  • First fixed AsyncOS releases are 15.5.5-014 and 16.5.0-780. The 16.0 train has no fix and must migrate [1][2]. Content Scanner Tools 25.3.0.5525 delivers the fix without an upgrade or restart [1][6].
  • Cisco says the flaw “was found during internal security scanning” [1]. The hardening release credits existing test processes and frontier AI models [2]. The September SQL injection advisory gives a different origin: the resolution of a TAC support case [3].
  • CISA added CVE-2026-76519 to the Known Exploited Vulnerabilities catalogue with a 17 October federal deadline, as reported by Rapid7, SecurityWeek and The Stack [5][8][9]. cisa.gov could not be retrieved, so the catalogue entry is cited through those publishers.
  • Cisco has deployed the fixed scanner across its managed Secure Email Cloud and contacted customers whose devices showed possible indicators of compromise [1][4]. No victim count or actor has been disclosed [4][6][7].

Where the sources diverge

Scope. The hardening release says its vulnerabilities affect both products regardless of device configuration [2]. The per-bug advisory narrows the exploited member to gateways with File Reputation enabled and an older scanner package [1]. Both are Cisco statements about the same flaw at different resolutions. For inventory, the bucket’s broader scope is the safer starting point.

Patch equivalence. Rapid7 states that the fixed versions for the two exploited CVEs are the same, and that customers who patched for CVE-2026-76461 should be covered for CVE-2026-76519 [9]. That holds on 15.5.5-014 and 16.5.0-780. It does not hold on the 16.0 train. Cisco lists 16.0.4-302 as the first fixed 16.0 build for the SQL injection [3][10]. The file write advisory gives no 16.0 fix and says migrate [1]. The Hacker News reports that 16.0.4-302 does not fix the new flaw [4]. An estate that took 16.0.4-302 in September closed the first exploited bug and left the second open, unless its scanner package reached 25.3.0.5525 independently [1].

Build strings. September press coverage printed 15.5.5-0141 [10][11] and, in one case, 16.0.4-3021 [11]. Cisco’s advisory tables read 15.5.5-014 and 16.0.4-302 [1][3]. Use the vendor tables.

What it means

A class-level CVE tells the operator that a critical flaw exists, not where it sits. For a month the CWE-23 bucket carried a 9.8 rating and a configuration-independent scope with no per-bug detail [2]. Its revision history records one change, on 14 October, adding the link to the related advisory [2]. Operators who patched on the bucket alone were already covered. Operators who waited for an exploitation signal were not.

Cisco does not say whether exploitation began before or after the September fix shipped [1]. The timing is consistent with either independent discovery or work from the patch. Neither is established, and this desk does not assume one.

Detection is constrained by the privilege the bug grants. Cisco’s on-box check reports one of three results from a system log scan [1]. A clean result is not proof, because root access allows evidence to be hidden [1][4]. Cluster members trust one another through SSH key pairs, so one compromised member puts the cluster at risk [1][6]. Upgrading a compromised virtual instance destroys its forensic data [1].

The same day, a different shape

Palo Alto Networks published CVE-2026-0322 on 14 October [14]. It is a code injection in the PAN-OS management interface. An authenticated attacker with network access can execute code as root on PA-Series and VM-Series firewalls and Panorama. Cloud NGFW and Prisma Access are not affected [14]. The CVSS 4.0 score is 8.6, with high privileges required, exploit maturity recorded as attacked and suggested urgency set to highest [14]. The vendor reports very limited exploitation against the management interface and says no special configuration is required [14][15]. It was also found internally [14]. CISA added it to the catalogue alongside the Cisco flaw, according to The Hacker News [15].

The two advisories describe different exposure models. The PAN-OS flaw needs administrative access to a management plane that operators can restrict to a jump host [14]. Exploitation in the wild means an attacker reached that interface with sufficient privilege; the advisory does not say how [14]. The Cisco flaw needs only that an email reach the gateway [1]. Mail flow cannot be fenced the way a management port can.

What to do

  • Record, per gateway and per cluster member, the AsyncOS train, the Content Scanner Tools version and File Reputation status on every mail policy [1].
  • On 16.0, treat 16.0.4-302 as not fixed for CVE-2026-76519. Migrate to 16.5.0-780 or confirm the scanner is at 25.3.0.5525 or later [1][3].
  • Enable automatic service updates so scanner fixes land without a software upgrade [1].
  • Run the vendor compromise check on every cluster member, then review external firewall and network logs for unexpected uploads and downloads [1][7].
  • For suspected compromise of a virtual gateway, preserve forensic data first, deploy a fresh instance, rebuild configuration without importing old files, renew credentials and cryptographic material, and restore every cluster member [1].
  • Separate mail and management interfaces, disable unneeded services and forward logs off-box [1].
  • For PAN-OS, move to the fixed hotfix on the running branch and restrict management access to a jump host. Threat Prevention signatures give limited coverage and only with inbound management traffic decrypted [14][15].
  • Patch to the fixed release named in any hardening release on its own merits, without waiting for a per-bug advisory [2].

The OFFSEC read

One Cisco bucket has now produced two exploited bugs in five weeks [2][3]. A class-level CVE is not a lower-risk disclosure. It is the same defect with less information attached. Rapid7 reported that 62 per cent of vulnerabilities exploited in the second quarter required no user interaction [16]. Both email gateway bugs fit that pattern: delivery of a message is the whole precondition [1][3]. Patch on the hardening release. Do not wait for its contents to be named.

Sources

Every R3KONX article cites its primary material. 16 sources, in order of first citation. Links open the original publication.

  1. Cisco Secure Email Gateway Arbitrary File Write Vulnerability (cisco-sa-esa-afw-zqYJkjxp) Cisco · 2026-10-14
  2. Cisco Secure Email Gateway and Secure Email and Web Manager Security Hardening Release: September 2026 Cisco · 2026-10-14
  3. Cisco Secure Email Gateway SQL Injection Vulnerability (cisco-sa-esa-inj-2bLVGmhX) Cisco · 2026-09-17
  4. Cisco Warns of Active Attacks Exploiting New Critical Secure Email Gateway Vulnerability The Hacker News · 2026-10-14
  5. Cisco Warns of Exploited Secure Email Gateway Vulnerability SecurityWeek · 2026-10-15
  6. Cisco warns of actively exploited Secure Email Gateway flaw CSO Online · 2026-10-15
  7. Cisco Email Gateway Zero-Day Under Attack, Root Access at Risk eSecurity Planet · 2026-10-15
  8. CISA adds Cisco CVE to KEV The Stack · 2026-10-15
  9. ETR: CVE-2026-76461 Critical Cisco Secure Email Gateway Vulnerability Exploited in the Wild Rapid7 · 2026-10-16
  10. Cisco Secure Email Gateway Flaw Exploited The Hacker News · 2026-09-15
  11. Critical Cisco Secure Email Gateway zero-day gives attackers root access CSO Online · 2026-09-15
  12. U.S. CISA adds Cisco Secure Email Gateway flaw to its Known Exploited Vulnerabilities catalog Security Affairs · 2026-09-15
  13. CVE-2026-76440 The Hacker Wire · 2026-09-15
  14. CVE-2026-0322 PAN-OS: Authenticated Remote Code Execution in the Management Interface Palo Alto Networks · 2026-10-15
  15. Palo Alto Networks Patches PAN-OS Flaw Exploited in Attacks The Hacker News · 2026-10-15
  16. New Report: AI threats are here. Why Q2 2026 signals the end of traditional patch cycles Rapid7 · 2026-08-18

Researched and written by the R3KONX analysis desk from the cited primary material. Methodological caveat: the CISA catalogue could not be retrieved, so Known Exploited Vulnerabilities dates are cited through publishers that state them, and neither vendor has disclosed exploitation scale. Corrections to event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.