# CVE-2026-110934: Other in Vyond

> Improper array index validation in Samsung Vyond allows attackers to manipulate input data, requiring a patch to mitigate.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-c3v3-9vv9-jppx

## What is CVE-2026-110934?

CVE-2026-110934 is a medium-severity vulnerability in Samsung Open Source Vyond, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper validation of array index vulnerability in Samsung Open Source Vyond allows Input Data Manipulation.

This issue affects Vyond: before be6e297b0c4836e20d73b2f8a40a561ea496ebaa.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2026-110934?


## How do I fix CVE-2026-110934?

No fix has been published for CVE-2026-110934 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110934 being exploited?

There is no known exploitation of CVE-2026-110934 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110934 and fix it if it is affected.

What it is: CVE-2026-110934 is a medium-severity vulnerability in Samsung Open Source Vyond, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110934 in the wild and no public exploit code.

Affected product: Samsung Open Source Vyond. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110934/ (Markdown: https://insights.sbomify.com/CVE-2026-110934/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110934
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110934
- OSV: https://osv.dev/vulnerability/CVE-2026-110934

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110934/
Summaries are generated and may contain mistakes; the official description above is the record.