Always-Incorrect Control Flow Implementation in Suricata - #VU162650
Published: November 9, 2026
Vulnerability details
The vulnerability allows an unauthenticated remote attacker to cause spurious alerts and unintended file storage in Suricata.
The vulnerability exists due to skipped leading file keyword constraints when Suricata inspects the second and later files in crafted multi-file transactions using rules with multiple file keywords. An unauthenticated remote attacker can submit such transactions to generate incorrect matches and store excluded files when file storage is enabled and filestore is the trailing keyword.