CVE-2026-20026

A vulnerability in the VBA feature of the Snort 3 engine in multiple Cisco products allows an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to crash. This is due to lack of proper error checking when decompressing VBA data. A successful exploit could cause the engine to unexpectedly restart, leading to a DoS condition.

A vulnerability in the VBA feature of the Snort 3 engine in multiple Cisco products allows an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to crash. This is due to improper error checking when decompressing VBA data. A successful exploit could cause the engine to enter an infinite loop, leading to a DoS condition.

A vulnerability in the VBA feature of the Snort 3 engine in multiple Cisco products allows an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to crash. This is due to improper range checking when decompressing user-controlled VBA data. A successful exploit could cause an overflow of heap data, leading to a DoS condition.

Multiple Cisco products are affected by an out-of-bounds read in buffer handling when processing DCE/RPC requests in the Snort 3 Detection Engine. An unauthenticated remote attacker could send many requests over an established connection to obtain sensitive information from the Snort 3 data stream.

Multiple vulnerabilities in the SMB2 processor of the Snort detection engine on multiple Cisco products could allow an unauthenticated, remote attacker to bypass configured policies or cause a denial of service (DoS) condition. This is due to improper management of system resources when processing SMB2 traffic. An attacker could send a high rate of SMB2 packets to trigger a reload of the Snort process. With preserve-connection enabled (default), policy bypass and malicious payload delivery are also possible.

A vulnerability in the Snort detection engine of multiple Cisco products could allow an unauthenticated, remote attacker to bypass a configured file policy for HTTP. The issue is due to incorrect handling of specific HTTP header parameters. An attacker could exploit this by sending crafted HTTP packets through an affected device, bypassing the policy and delivering a malicious payload.