Read the docs

Memory exhaustion in Zeek MIME parser via folded header lines

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 8.2.1 are affected. Parsing a folded MIME header allocates memory for each continuation line, so crafted input with many continuation lines can exhaust memory. The fix caps continuation lines with the configurable MIME::max_header_continuation_lines setting, which defaults to 1000.

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

Description from the GitHub advisory

### Description of issue Parsing a folded MIME header can consume significant amounts of memory. While there's a MIME::max_header_bytes defaulting to 64k bytes, crafted input can use continuation lines to fill this limit increasing memory usage due to allocations for each folded line. ### Impact/Category This is a memory exhaustion vulnerability in the MIME parser. ### Fix included MIME header parsing now limits the allowed number of continuation lines for folded MIME headers to a configurable limit (MIME::max_header_continuation_lines, default: 1000). If exceeded, a new exceeded_mime_max_continuation_lines weird is raised.

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-xvj8-9xvq-g5qq
  • zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.11, 9.0.1 Patch available GHSA-xvj8-9xvq-g5qq

Remediation

Upgrade Zeek to version 8.0.11 or 9.0.1.

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

  • Fix · GHSA-xvj8-9xvq-g5qq zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-xvj8-9xvq-g5qq

References

Sources

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