LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24818: A heap-based buffer over-read that might affect a system that compiles untrusted Lua code in praydog/UEVR

Out-of-bounds Read vulnerability in praydog UEVR (dependencies/lua/src modules). This vulnerability is associated with program files lparser.C. This issue affects UEVR: before 1.05.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24818 is a memory read flaw in praydog UEVR’s bundled Lua parser. It matters mainly where UEVR compiles Lua code supplied by untrusted users or sources. The issue affects UEVR before 1.05 and may expose limited data or cause limited availability impact. No public source provided indicates active exploitation.

Executive priority

Treat as a targeted, moderate-priority update. Prioritize faster if UEVR is used with community, plugin, mod, or other untrusted Lua inputs. Otherwise, handle through normal patch management while confirming whether the vulnerable parsing path is reachable.

Technical view

The CVE describes a CWE-125 out-of-bounds read in dependencies/lua/src, associated with lparser.C. CVSS 4.0 score is 6.9. The vulnerable condition is tied to compiling untrusted Lua code. Public data identifies UEVR versions before 1.05 as affected and references a GitHub pull request tagged as a patch.

Likely exposure

Exposure is likely limited to UEVR deployments or builds that include the affected Lua parser and process untrusted Lua input. Systems not using UEVR, not before 1.05, or not compiling untrusted Lua are less likely to be exposed based on the provided sources.

Exploitation context

The sources do not report active exploitation, and the CVE is not listed as KEV in the provided bundle. Exploitation would require reaching the Lua compilation path with crafted untrusted Lua input. The reported impact is read-related memory exposure and limited availability impact, not confirmed code execution.

Researcher notes

Evidence is limited to the CVE record, CVE List data, and the referenced GitHub pull request. The affected-version field in the bundle is sparse, but the description states UEVR before 1.05. No source provided confirms exploit availability or exploitation in the wild.

Mitigation direction

  • Upgrade UEVR to 1.05 or later if using an affected version.
  • Review the referenced GitHub patch before maintaining custom forks.
  • Avoid compiling Lua code from untrusted sources until remediated.
  • Monitor praydog UEVR advisories for any updated guidance.

Validation and detection

  • Inventory UEVR versions in use across affected environments.
  • Confirm whether any deployment compiles user-supplied or third-party Lua code.
  • Verify patched source includes the fix referenced in PR 337.
  • Document systems below 1.05 for upgrade prioritization.
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-24818 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
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:L/S:N/AU:Y/R:U/V:D/RE:L/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
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:L/S:N/AU:Y/R:U/V:D/RE:L/U:Amber——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-24818Attack 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:L/VI:N/VA:L/SC:L/SI:N/SA:L/S:N/AU:Y/R:U/V:D/RE:L/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
praydogUEVR0unaffected
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.