Read the docs

Unbounded IMAP capability parsing in Zeek allows memory exhaustion

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 versions up to and including 8.0.9 and up to and including 8.2.1 are affected when the imap_capabilities() event is implemented. The IMAP parser stores and raises an unbounded number of IMAP capabilities. An attacker who sends crafted IMAP traffic can exhaust the memory of the Zeek process.

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

Description from the GitHub advisory

### Description of issue When the `imap_capabilities()` event is implemented, Zeek would intermediately store and raise an unbounded amount of IMAP capabilities. This could result in a memory exhaustion with crafted traffic. ### Impact/Category This is a potential memory exhaustion vulnerability in the IMAP parser. ### Fix included Zeek now limits the number of IMAP capabilities stored to IMAP::max_capabilities (default: 100) and raises a new imap_max_capabilities_reached weird when this limit is reached.

Why it matters now

Fix Fixed zeek (zeek): 8.0.11, 9.0.1

SSVC decision points

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

Affected products

VendorProductAffected versionsFixed inStatusSource
—zeek (zeek)<=8.0.9, <=8.2.18.0.11, 9.0.1Patch availableGHSA-2prg-45gv-3rg9
  • zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.11, 9.0.1 Patch available GHSA-2prg-45gv-3rg9

Remediation

Upgrade Zeek to 8.0.11 or 9.0.1. The fixed releases limit stored capabilities to IMAP::max_capabilities (default: 100) and raise the imap_max_capabilities_reached weird when that limit is hit.

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

  • Fix · GHSA-2prg-45gv-3rg9 zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-2prg-45gv-3rg9

References

Sources

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