# CVE-2026-82989: CVE-2026-82989

> Remote unauthenticated attackers can inject arbitrary input into ViewSonic ViewBoard vCast services via HTTP requests, potentially leading to code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-wx6m-rmf7-wpp6

## What is CVE-2026-82989?

CVE-2026-82989 is a critical code injection vulnerability in Viewsonic vCast, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is an input injection in vCast exposed network services in ViewSonic ViewBoard that allows a remote, unauthenticated attacker to inject arbitrary input into service endpoints via network-based HTTP requests to unauthenticated endpoints

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-147 (Improper Neutralization of Input Terminators)

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


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

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

## Is CVE-2026-82989 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82989 is a critical code injection vulnerability in Viewsonic vCast, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82989 in the wild and no public exploit code.

Affected product: Viewsonic vCast. 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-82989/ (Markdown: https://insights.sbomify.com/CVE-2026-82989/index.md)
```

## Sources

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

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