Service interruption via Lua stack exhaustion
Published Jan 27, 2026 · Updated Jan 27, 2026
Out-of-bounds reads in Wicked Engine before 0.71.705 allow local users to interrupt service through Lua error handling. When C stack overflow occurs during error handling, ldebug.c leaves redundant messages on the Lua stack, causing excessive stack consumption. Low-privileged local access and active user interaction are required; successful exploitation exhausts the stack and causes denial of service without reported data disclosure or modification.
Summary
What happened
Out-of-bounds reads in Wicked Engine before 0.71.705 allow local users to interrupt service through Lua error handling. When C stack overflow occurs during error handling, ldebug.c leaves redundant messages on the Lua stack, causing excessive stack consumption. Low-privileged local access and active user interaction are required; successful exploitation exhausts the stack and causes denial of service without reported data disclosure or modification.
The record
- CVE
- CVE-2026-24820
- Published
- Jan 27, 2026
- Updated
- Jan 27, 2026
- Vendor
- Turánszki János
- Product
- Wicked Engine
- Classifications
- CWE-125, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2026CVE publishedPublication date reported by the CVE source.
- Jan 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.71.705
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo