Memory corruption via overflowing alert queue capacity
Published Jan 27, 2026 · Updated Jan 27, 2026
Use-after-free in Suricata before 7.0.14 and 8.0.0 through 8.0.2 allows remote attackers to corrupt memory via one packet. AlertQueueExpand in src/detect-engine-alert.c doubles the 16-bit alert_queue_capacity without a boundary check, so the value wraps while queue storage is reallocated. Exploitation requires a ruleset with at least 65,536 signatures matching that packet and can crash the engine or corrupt its process memory.
Summary
What happened
Use-after-free in Suricata before 7.0.14 and 8.0.0 through 8.0.2 allows remote attackers to corrupt memory via one packet. AlertQueueExpand in src/detect-engine-alert.c doubles the 16-bit alert_queue_capacity without a boundary check, so the value wraps while queue storage is reallocated. Exploitation requires a ruleset with at least 65,536 signatures matching that packet and can crash the engine or corrupt its process memory.
The record
- CVE
- CVE-2026-22264
- Published
- Jan 27, 2026
- Updated
- Jan 27, 2026
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-416, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2026CVE publishedPublication date reported by the CVE source.
- Jan 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.0.14
- Affected versionversion=>= 8.0.0, < 8.0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo