VulnerabilityPublished 7 Jul 2025Updated 3 Nov 2025

CVE-2024-25178: LuaJIT · Out-of-bounds Read

Affects LuaJITSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.1-20240314 as a priority.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% 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:H/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade openresty/luajit2 to 2.1-20240314.

Affected software

Product	Affected	Fixed in
GitHubluajit/LuaJIT`pkg:github/luajit/LuaJIT`Other threats	Affected <=2.1	Fixed in–
GitHubopenresty/luajit2`pkg:github/openresty/luajit2`Other threats	Affected <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

Immediately inventory all systems and applications using LuaJIT or OpenRusty luajit2 to identify vulnerable versions.
Restrict network access to services and applications embedding LuaJIT, especially those exposed to untrusted networks, using firewalls and network segmentation.
Implement application-level monitoring and alerting for crashes or abnormal behavior indicative of exploitation attempts.
Employ runtime protection mechanisms such as sandboxing or containerization to limit the impact of potential crashes.
6. Consider temporary workarounds such as disabling LuaJIT scripting features if feasible without impacting critical functionality. 7. Conduct penetration testing and vulnerability scanning focused on LuaJIT components to validate the effectiveness of mitigations. 8. Educate development and operations teams about the vulnerability to ensure rapid response and patch management. 9. Maintain up-to-date backups and incident response plans to recover quickly from potential denial-of-service attacks.

Description

LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.

Impact

The primary impact of CVE-2024-25178 is a denial-of-service condition caused by out-of-bounds reads in the stack-overflow handler, which can crash applications or systems embedding LuaJIT. For European organizations, this can disrupt critical services, especially those relying on LuaJIT for scripting in network devices, industrial control systems, or software platforms. The high confidentiality impact rating suggests potential information leakage risks, although no integrity impact is noted. The vulnerability's network accessibility and lack of required privileges increase the risk of widespread exploitation. Disruptions could affect sectors such as telecommunications, manufacturing, finance, and government services that utilize LuaJIT-based components. The absence of known exploits currently provides a window for proactive mitigation, but the critical severity demands urgent attention to prevent potential future attacks. Additionally, the impact on availability could lead to operational downtime, financial losses, and reputational damage for affected organizations.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 18:46 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats