# CVE-2026-123993: Hisense VIDAA Smart TV Unauthenticated WebDriver Remote Access


- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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-fc56-2cmc-39gc

## What is CVE-2026-123993?

CVE-2026-123993 is a high-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 where a QA build of the Google Cobalt browser engine exposes the WebDriver automation server on TCP port 4444 across all network interfaces without any authentication or pairing requirement. A LAN-adjacent attacker can connect to the exposed WebDriver service to execute arbitrary JavaScript, read and exfiltrate sensitive localStorage data including ACR telemetry, MAC addresses, ad-service credentials, and location data, inject persistent content onto the display, and access the window.hisense native bridge to perform filesystem read/write and system-state operations.

Weakness: CWE-489 (Active Debug Code), CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-123993 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123993 is a high-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-123993 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-123993/ (Markdown: https://insights.sbomify.com/CVE-2026-123993/index.md)
```

## Sources

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

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