# CVE-2026-123995: Hisense VIDAA Smart TV SSRF via SetAVTransportURI CurrentURI


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-32qr-wwq4-8qhm

## What is CVE-2026-123995?

CVE-2026-123995 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 input validation vulnerability in the UPnP/DLNA AVTransport SOAP service that allows a LAN-adjacent attacker to inject arbitrary URIs via the CurrentURI field of SetAVTransportURI without validating the scheme, host, or media legitimacy. Attackers can supply schemes such as http://, file:///data/misc/wifi/, rtsp://, or smb:// to have the TV fetch and render attacker-controlled content after a one-time DLNA pairing, enabling phishing pages, fake firmware prompts, and fake emergency alerts to be displayed, with subsequent commands executing silently.

Weakness: CWE-451 (User Interface (UI) Misrepresentation of Critical Information), CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-123995 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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