CVE-2026-110934
Deferred Deferred - Pending Action

Improper Array Index Validation in Samsung Vyond

Vulnerability report for CVE-2026-110934, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-15

Last updated on: 2026-10-15

Assigner: Samsung TV & Appliance

Description

Improper validation of array index vulnerability in Samsung Open Source Vyond allows Input Data Manipulation. This issue affects Vyond: before be6e297b0c4836e20d73b2f8a40a561ea496ebaa.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-15
Last Modified
2026-10-15
Generated
2026-10-19
AI Q&A
2026-10-15
EPSS Evaluated
2026-10-18
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Samsung Open Source Vyond 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-129 The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an improper validation of array index issue in Samsung Open Source Vyond. It allows input data manipulation by enabling access to an out-of-bounds memory location in the ENCLAVES array due to missing bounds checking on a user-controlled parameter called eid. The original code directly accessed the array without verifying if eid was within valid bounds, which could lead to a panic from out-of-bounds access.

The fix adds a bounds check to return early if the index is invalid, preventing the out-of-bounds panic. This change affects all SBI functions that rely on the find_enclave() function with user-supplied eid values.

Detection Guidance

This vulnerability involves improper array index validation in Samsung Open Source Vyond's find_enclave() function. To detect it, inspect the code for direct array access without bounds checking on user-controlled eid parameters. Look for instances where ENCLAVES[eid] is accessed without prior validation of eid against MAX_ENCLAVES. The fix adds a conditional check (if eid >= MAX_ENCLAVES) to prevent out-of-bounds access.

Impact Analysis

This vulnerability could cause the application to crash due to a panic from out-of-bounds memory access. It may also allow an attacker to manipulate input data by exploiting the missing bounds check, potentially leading to unexpected behavior or further security issues in the system.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it involves an out-of-bounds memory access in Samsung Open Source Vyond, which is a technical implementation issue rather than a data protection or privacy violation. Compliance impacts would depend on whether this flaw leads to unauthorized data access or processing, which is not specified in the provided context.

Mitigation Strategies

Update Samsung Open Source Vyond to the fixed commit be6e297b0c4836e20d73b2f8a40a561ea496ebaa or later to ensure bounds checking is applied to the eid parameter in the find_enclave() function.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-110934. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart