{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-45763 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-45763 is a medium-severity denial of service vulnerability in Oisf Suricata, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45763 and fix it if it is affected.\n\nWhat it is: CVE-2026-45763 is a medium-severity denial of service vulnerability in Oisf Suricata, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-45763 in the wild and no public exploit code.\n\nAffected product: Oisf Suricata. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45763/ (Markdown: https://insights.sbomify.com/CVE-2026-45763/index.md)","id":"CVE-2026-45763","markdown":"https://insights.sbomify.com/CVE-2026-45763/index.md","name":"CVE-2026-45763","record":{"aliases":["DEBIAN-CVE-2026-45763","GHSA-9h43-frr8-xx6m","UBUNTU-CVE-2026-45763"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Network IDS/IPS","requires_auth":"none","summary":"Attackers can cause denial of service in Suricata by exceeding Lua sandbox memory limits when Lua rules are enabled.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"suricata","vendor":"oisf"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Suricata lua: sandbox allocation limit not enforced for new allocations","id":"CVE-2026-45763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oisf:suricata","products":["oisf:suricata"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Suricata http2: protocol-change type confusion can lead to denial of service","id":"CVE-2026-45764"},"packages":[],"prev":{"headline":"Suricata defrag: missing address-family check can lead to remote crash","id":"CVE-2026-45762"},"products":["suricata"],"published":"2026-09-10","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-35853","kev_date_added":null,"published":"2023-06-19"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2021-37592","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2018-10244","kev_date_added":null,"published":"2019-04-04"},{"cvss_score":9.4,"headline":"Memory corruption in Suricata","id":"CVE-2026-94083","kev_date_added":null,"published":"2026-09-20"},{"cvss_score":9.4,"headline":"Use after free in Suricata","id":"CVE-2026-94084","kev_date_added":null,"published":"2026-09-20"},{"cvss_score":9.1,"headline":"Suricata http2: protocol-change type confusion can lead to denial of service","id":"CVE-2026-45764","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":8.2,"headline":"Suricata smtp/mime: heap out-of-bounds read quoted-printable decoder","id":"CVE-2026-57228","kev_date_added":null,"published":"2026-09-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["OISF"]},"summary":"Attackers can cause denial of service in Suricata by exceeding Lua sandbox memory limits when Lua rules are enabled.","url":"https://insights.sbomify.com/CVE-2026-45763/"}