LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24821: A heap-based buffer over-read that might affect a system that compiles untrusted Lua code in turanszkij/WickedEngine.

Out-of-bounds Read vulnerability in turanszkij WickedEngine (WickedEngine/LUA modules). This vulnerability is associated with program files lparser.C. This issue affects WickedEngine: through 0.71.727.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-24821 is a critical out-of-bounds read in WickedEngine’s Lua parsing code. The main business concern is systems that compile untrusted Lua code, where malformed input may expose memory or disrupt availability. The provided sources show a patch reference, but no evidence of active exploitation.

Executive priority

Prioritize if WickedEngine is used in exposed applications or user-content workflows. For internally controlled or trusted-script-only deployments, treat as important patch management rather than an emergency, while monitoring vendor release guidance.

Technical view

The issue is CWE-125 in WickedEngine/LUA modules, associated with lparser.C. WickedEngine through 0.71.727 is listed as affected. CVSS 4.0 score is 9.3, with network attack vector, low complexity, no privileges, no user interaction, high confidentiality impact, and high availability impact.

Likely exposure

Exposure is most likely where WickedEngine is embedded in applications, tools, games, or services that accept or compile Lua from untrusted users or external content. Systems that only run trusted bundled scripts have a narrower exposure, but should still track the vendor patch.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk comes from remotely reachable or user-facing Lua compilation paths, especially where attackers can submit crafted Lua code for parsing.

Researcher notes

Evidence is limited to the CVE record and the referenced GitHub patch. Do not assume broader exploitability beyond the described Lua parser out-of-bounds read. Key research questions are reachability of Lua compilation, trust boundary, and whether downstream products vendor WickedEngine code.

Mitigation direction

  • Review the GitHub patch pull request and vendor guidance.
  • Upgrade or backport the patch once a trusted fixed build is available.
  • Disable or restrict compilation of untrusted Lua where feasible.
  • Limit Lua submission features to authenticated and trusted users.
  • Add input-handling safeguards around external Lua content.

Validation and detection

  • Inventory products embedding WickedEngine through version 0.71.727.
  • Identify whether Lua compilation accepts untrusted or external input.
  • Check whether the lparser.C patch from PR 1095 is present.
  • Review crash, memory, and parser error telemetry for unusual Lua inputs.
  • Track CVE and vendor repository updates for fixed release details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24821 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:H/SI:N/SA:H/S:N/AU:Y/R:U/V:D/RE:M/U:Amber

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:H/SI:N/SA:H/S:N/AU:Y/R:U/V:D/RE:M/U:Amber——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-24821Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:H/SI:N/SA:H/S:N/AU:Y/R:U/V:D/RE:M/U:Amber

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
turanszkijWickedEngine0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.