Unbounded TLS extension parsing in Zeek can exhaust memory
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. The default Binpac SSL analyzer parsed TLS extensions without checking their length. A remote attacker can send an endless stream of extensions to exhaust parser memory and crash Zeek.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Description of issue The Binpac (default) SSL analyzer parsed extensions without checking the length. Doing so allowed an endless stream of extensions to exhaust parser memory, crashing Zeek. ### Impact/Category This is a denial-of-service risk due to the possibility of receiving these packets from remote systems. ### Fix included The parsed extension length is now used to bound the number of extensions. This is a `uint16`, meaning now extensions are limited to 65,535.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | zeek (zeek) | <=8.0.9, <=8.2.1 | 8.0.11, 9.0.1 | Patch available | GHSA-j2wq-86vc-93cg |
- zeek (zeek) Vendor— Affected <=8.0.9, <=8.2.1 Fixed in 8.0.11, 9.0.1 Patch available GHSA-j2wq-86vc-93cg
Remediation
Fixed Zeek versions are 8.0.11 and 9.0.1.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-j2wq-86vc-93cg zeek (zeek) Fixed in 8.0.11, 9.0.1 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-j2wq-86vc-93cg
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences