Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Starting in version 8.0.0 and prior to version 8.0.5, when Lua rule execution is enabled, the Lua sandbox memory limit was not consistently enforced for new allocations. Certain Lua allocation patterns could exceed security.lua.max-bytes without triggering the intended memory limit, making the configured sandbox limit unreliable. This requires Lua rules to be enabled and an affected Lua script/rule to be loaded. Version 8.0.5 contains a fix. As a workaround, disable security.lua.allow-rules unless Lua rules are required.
CVE-2026-45763
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
September 10, 2026
Last Modified
September 10, 2026
Advisory Details (2)
Auto-updated Sep 10, 2026lua: sandbox allocation limit not enforced for new allocations · Advisory · OISF/suricata · GitHub
https://github.com/OISF/suricata/security/advisories/GHSA-9h43-frr8-xx6mWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 20:15 UTCEPSS rescore
- 2026-09-20 00:53 UTCEG score recompute
- 2026-09-19 00:23 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 23:54 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 22:57 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 22:27 UTCEG score recompute
- 2026-09-13 21:28 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 20:59 UTCEG score recompute
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 20:30 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 18:22 UTCEG score recompute
- 2026-09-10 17:50 UTCEG score recompute
- 2026-09-10 14:19 UTCEG score recompute
- 2026-09-10 13:30 UTCEG score recompute
- 2026-09-10 13:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-45763?
When was CVE-2026-45763 disclosed?
Is CVE-2026-45763 actively exploited?
What is the CVSS score of CVE-2026-45763?
How do I remediate CVE-2026-45763?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-45763
Is Your Infrastructure Affected by CVE-2026-45763?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.