# CVE-2026-123994: Hisense VIDAA Smart TV DIAL Service Unauthenticated Access


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-h68h-965v-xmp9

## What is CVE-2026-123994?

CVE-2026-123994 is a medium-severity vulnerability in Hisense VIDAA, published on 6 Nov 2026. 

### Official description

Hisense VIDAA Smart TV firmware V0000.01.00a.P0220 contains an unauthenticated access vulnerability in the DIAL (Discovery and Launch) service on TCP port 56789, which accepts control requests from any LAN-adjacent device without authentication, pairing, or user notification. Attackers can query running application states, enumerate installed applications via HTTP response codes, terminate active sessions with a DELETE request, and launch applications or bypass YouTube's Origin check by spoofing the Origin header to disclose viewing activity and subscriptions or disrupt device functionality.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-123994 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123994 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123994 is a medium-severity vulnerability in Hisense VIDAA, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123994 exists.

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

## Sources

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

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