LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24817: A potential heap-buffer overflow in praydog/UEVR

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

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24817 is a high-severity memory corruption issue in praydog UEVR before version 1.05. The flaw is an out-of-bounds write in bundled Lua source files. Public sources do not show active exploitation. Organizations using UEVR should prioritize identifying any pre-1.05 installations and moving to the fixed version or vendor patch path.

Executive priority

Prioritize remediation for teams or users running UEVR before 1.05, especially where the tool is broadly deployed or exposed to externally sourced content. Business urgency is high because memory corruption can cause service disruption, but current public evidence does not show active exploitation.

Technical view

The CVE describes CWE-787 out-of-bounds write in praydog UEVR dependencies/lua/src modules, specifically ldebug.C and lvm.C. The reported CVSS 4.0 score is 8.7. The CVSS vector indicates network attackability, low complexity, no privileges, no user interaction, high vulnerable-system availability impact, and low subsequent-system availability impact.

Likely exposure

Exposure appears limited to environments running praydog UEVR before 1.05. The provided affected data is sparse and internally awkward, listing version “0” while the description states “before 1.05.” Validate against actual installed UEVR versions and vendor release artifacts.

Exploitation context

The source bundle does not cite exploitation in the wild, and the CVE is not marked in KEV. No public exploit status is established here. Treat this as a serious memory-safety vulnerability, but do not assume active exploitation without new vendor, KEV, or credible public reporting.

Researcher notes

Evidence is limited to the CVE record, CVE List JSON, and GitHub PR 336. The affected-version metadata is less precise than the description. Avoid inferring exploitability beyond the CVSS vector and CWE. Focus validation on version confirmation and whether the Lua-related patch is present.

Mitigation direction

  • Upgrade praydog UEVR to version 1.05 or later.
  • Review GitHub pull request 336 for the vendor patch context.
  • If upgrade is not possible, check vendor guidance for interim controls.
  • Track the CVE record for updated affected-version details.

Validation and detection

  • Inventory systems where praydog UEVR is installed.
  • Flag any UEVR version earlier than 1.05.
  • Confirm the installed build includes the PR 336 fix.
  • Document exceptions where UEVR cannot be upgraded promptly.
  • Monitor CVE and vendor sources for revised advisories.
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-787: 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-24817 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
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-24817Attack 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:N/VI:N/VA:H/SC:N/SI:N/SA:L/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
praydogUEVR0unaffected
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

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