Skip to main content
CVE-2024-25177VulnerabilityPublished Updated

CVE-2024-25177: LuaJIT · n/a

Affects LuaJITSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 2.1-20240314 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1-20240314
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade openresty/luajit2 to 2.1-20240314.

Affected software

ProductAffectedFixed in
GitHubluajit/LuaJITpkg:github/luajit/LuaJITOther threatsAffected
  • <=2.1
Fixed in–
GitHubopenresty/luajit2pkg:github/openresty/luajit2Other threatsAffected
  • <2.1-20240314
Fixed in
  • 2.1-20240314

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should monitor LuaJIT project updates and apply the fixed version v2.1-20240314 or later as soon as it becomes available. If you cannot patch yet, organizations should audit their software stacks to identify LuaJIT usage, including indirect dependencies. Employ runtime application self-protection (RASP) or memory safety tools to detect abnormal memory access patterns indicative of exploitation attempts. Network-level protections such as Web Application Firewalls (WAFs) can be tuned to detect and block suspicious Lua script payloads or malformed inputs targeting LuaJIT engines. For embedded systems, firmware updates incorporating patched LuaJIT versions should be prioritized. Additionally, implement robust monitoring and alerting for application crashes or unusual restarts that may signal exploitation attempts. Engage with vendors and suppliers to ensure timely patch deployment. Avoid exposing LuaJIT-powered services directly to untrusted networks without additional access controls.

Description

LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an unsinking of IR_FSTORE for NULL metatable, which leads to Denial of Service (DoS).

References

Community reviews

Loading reviews…