Read the docs

Memory exhaustion in Zeek event queue via crafted TCP streams

Priority LOW 38Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

Zeek up to and including 8.0.10 and 8.2.2 can exhaust memory through its event queue. When out-of-order TCP packets are reassembled, Zeek may pass large buffers of stream data to protocol parsers at once, creating millions of events because the event queue had no maximum size. A remote attacker can exploit this by sending crafted TCP streams, which drives Zeek into out-of-memory conditions and causes a denial of service.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Description of issue Various event queue memory exhaustion vulnerabilities have been reported that stem from the same root cause: In the face of out-of-order packets, Zeek's TCP reassembly logic may deliver large buffers of accumulated and reassembled stream data to protocol parsers at once, in turn potentially creating millions of events. Because Zeek's event queue previously had no maximum size, this scenario can be exploited by sending crafted TCP streams and increase Zeek's memory usage to the point of out-of-memory situations. ### Impact/Category This is a denial-of-service risk due to the possibility of receiving these packets from remote systems. ### Fix included A new option max_event_queue_size (default 2000) has been added. When the queue grows larger than this maximum during protocol parsing, Zeek will trigger an intermittent queue drain to keep the required memory for queued events bounded. A new weird event_queue_overflow_drain is raised whenever this happens and a new metric `zeek_event_queue_overflow_drains` incremented.

Why it matters now

Fix Fixed zeek (zeek): 8.0.11, 8.2.3

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—zeek (zeek)<=8.0.10, <=8.2.28.0.11, 8.2.3Patch availableGHSA-pwfv-247f-jfrh
  • zeek (zeek) Vendor— Affected <=8.0.10, <=8.2.2 Fixed in 8.0.11, 8.2.3 Patch available GHSA-pwfv-247f-jfrh

Remediation

Upgrade Zeek to 8.0.11 or 8.2.3. The fix adds the max_event_queue_size option (default 2000) that bounds the event queue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-pwfv-247f-jfrh zeek (zeek) Fixed in 8.0.11, 8.2.3 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-pwfv-247f-jfrh

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences