Medium [CVE-2026-76445] Multiple Cisco Products Snort 3 Denial of Service Vulnerability
This medium-severity Cisco advisory covers CVE-2026-76445 affecting Secure Firewall Threat Defense (FTD) Software, Firepower 2100 Series, Firepower 1000 Series.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Cisco CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
Multiple Cisco products are affected by a vulnerability in the Snort 3 Detection Engine that could allow an unauthenticated, remote attacker to cause the detection engine to unexpectedly restart, resulting in a denial of service (DoS) condition.
The vulnerability is due to a flaw in logic handling when General Packet Radio Service (GPRS) Tunneling Protocol (GTP) extension headers are processed within the codec. An attacker could exploit this vulnerability by sending a crafted, fragmented UDP datagram that contains these headers to the Snort 3 Detection Engine of an affected device.
A successful exploit could allow the attacker to cause the detection engine to enter an infinite loop, resulting in a DoS condition.
Cisco has released software updates that address this vulnerability. There are workarounds that address this vulnerability.
This advisory is part of a group of advisories. For a complete list of the advisories and links to them, see Cisco Advance Notification for Publication of October 21, 2026, Security Advisories.
In addition, for further documentation of improvements and fixes in Open Source Snort 3, see Multiple Cisco Products Snort 3 Security Hardening Release: October 2026.
Affected products named by the advisory: Secure Firewall Threat Defense (FTD) Software; Firepower 2100 Series; Firepower 1000 Series; ASA 5500-X Series Firewalls; and 4 more.
- Release 3.x (first fixed: 3.12.4.0)
- Release 17.12 (first fixed: 17.12.8)
- Release 17.15 (first fixed: 17.15.6)
- Release 17.18 (first fixed: 17.18.5)
- Release 26.1 (first fixed: 26.1.2)
- Release 26.2 (first fixed: 26.2.1)
Official advisory · high-confidence parse· fetched 16 hours ago·verify at source
- 3.12.4.0
- 17.12.8
- 17.15.6
- 17.18.5
- 26.1.2
- 26.2.1
Official advisory · high-confidence parse· fetched 16 hours ago·verify at source
Mitigation checklist
- Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
- Release 3.x: upgrade to 3.12.4.0.
- Release 17.12: upgrade to 17.12.8.
- Release 17.15: upgrade to 17.15.6.
- Release 17.18: upgrade to 17.18.5.
- Release 26.1: upgrade to 26.1.2.
- Release 26.2: upgrade to 26.2.1.
- There are no workarounds that address this vulnerability.
Official advisory · high-confidence parse· fetched 16 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.