# CVE-2026-123998: Hisense VIDAA Smart TV MQTT Broker Authentication Bypass


- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/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-hjch-8qgq-882h

## What is CVE-2026-123998?

CVE-2026-123998 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 authentication bypass vulnerability in its remote-control MQTT broker on TCP port 36669, which accepts publicly documented default credentials and an ineffective 4-digit pairing PIN with no rate limiting or lockout, allowing a brute force of the entire code space in about five seconds, while some actions require no pairing at all. A LAN-adjacent attacker can exploit this to inject key events, change volume, switch input sources, enumerate inputs, launch arbitrary installed applications, and monitor pairing activity, posing a significant risk in hotel deployments where untrusted LAN access is common.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts), CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2026-123998 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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