CVE-2024-25176: Critical severity LuaJit LuaJIT vulnerability
Last updated 16 July 2026
Other sources
LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a stack-buffer-overflow in ljstrfmtwfnum in ljstrfmtnum.c.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/luajitto a version that resolves this vulnerability.Fixed in 2.1.0~beta3+dfsg-5.3+deb11u1Fixed in 2.1.0~beta3+git20220320+dfsg-4.1+deb12u1Fixed in 2.1.0+openresty20250117-2Fixed in 2.1.0+openresty20251030-1 - Upgrade
Upgrade
LuaJITto a version that resolves this vulnerability.Fixed in 2.1-20240626
Event History
Frequently Asked Questions
What is the severity of CVE-2024-25176?
CVE-2024-25176 has been identified as a critical severity vulnerability due to the potential for stack buffer overflow leading to arbitrary code execution.
How do I fix CVE-2024-25176?
To fix CVE-2024-25176, upgrade LuaJIT to the latest version beyond 2.1-20240626 which addresses this vulnerability.
What software versions are affected by CVE-2024-25176?
CVE-2024-25176 affects LuaJIT versions through 2.1 and OpenRusty luajit2 versions before v2.1-20240626.
What type of vulnerability is CVE-2024-25176?
CVE-2024-25176 is classified as a stack-buffer-overflow vulnerability located in the lj_strfmt_wfnum function.
Can CVE-2024-25176 lead to data compromise?
Yes, CVE-2024-25176 can potentially lead to data compromise through arbitrary code execution via the stack buffer overflow.