Allocation of Resources Without Limits or Throttling in Suricata - #VU162646
Published: November 9, 2026
Vulnerability details
The vulnerability allows an unauthenticated remote attacker to exhaust Suricata sensor memory.
The vulnerability exists due to missing enforcement of the configured max-table-size limit when Suricata's HTTP/2 parser, enabled by default, processes an HPACK dynamic table size update. An unauthenticated remote attacker can send an oversized update followed by indexed headers across many flows, causing headers to remain allocated for each flow's lifetime with growth bounded only by stream.reassembly.depth.