Vulnerability Description
In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases involving valid stack levels and > options are mishandled. NOTE: The LuaJIT project owner states that the debug libary is unsafe by definition and that this is not a vulnerability. When LuaJIT was originally developed, the expectation was that the entire debug library had no security guarantees and thus it made no sense to assign CVEs. However, not all users of later LuaJIT derivatives share this perspective
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Luajit | Luajit | <= 2.0.5 |
| Moonjit Project | Moonjit | < 2.1.2 |
Related Weaknesses (CWE)
References
- https://github.com/LuaJIT/LuaJIT/pull/526Issue TrackingPatchThird Party Advisory
- https://github.com/LuaJIT/LuaJIT/pull/526Issue TrackingPatchThird Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/08/msg00022.html
FAQ
What is CVE-2019-19391?
CVE-2019-19391 is a vulnerability with a CVSS score of 9.1 (CRITICAL). In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases inv...
How severe is CVE-2019-19391?
CVE-2019-19391 has been rated CRITICAL with a CVSS base score of 9.1/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2019-19391?
Check the references section above for vendor advisories and patch information. Affected products include: Luajit Luajit, Moonjit Project Moonjit.