# CVE-2026-123997: Hisense VIDAA Smart TV Unauthenticated DoS via SetAVTransportURI


- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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-6pfw-v7rf-jx64

## What is CVE-2026-123997?

CVE-2026-123997 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 denial-of-service vulnerability in the UPnP/DLNA AVTransport SOAP service that allows LAN-adjacent attackers to freeze the entire television software layer by sending a crafted SetAVTransportURI request on TCP port 38400. Attackers can exploit this flaw without credentials to render the device completely unresponsive to remote control or front-panel input, requiring a physical power cycle to restore functionality.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-123997 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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