Sandbox bypass via flow-variable state corruption
Published Sep 10, 2026 · Updated Sep 10, 2026
Out-of-bounds write in Suricata 8.0.0 through 8.0.4 allows remote attackers to bypass the Lua sandbox via excessive flow variables. Lua flow-variable registration writes outside its intended storage when a loaded rule registers too many variables, corrupting detection state. An affected Lua script or rule must be loaded; the corruption can escape sandbox restrictions or crash the inspection engine.
Summary
What happened
Out-of-bounds write in Suricata 8.0.0 through 8.0.4 allows remote attackers to bypass the Lua sandbox via excessive flow variables. Lua flow-variable registration writes outside its intended storage when a loaded rule registers too many variables, corrupting detection state. An affected Lua script or rule must be loaded; the corruption can escape sandbox restrictions or crash the inspection engine.
The record
- CVE
- CVE-2026-45770
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-787, CWE-693
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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=>= 8.0.0, < 8.0.5
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