# CVE-2026-58378: Allwinner TV Box TV98 ADB exposed on network

> Attackers can gain root privileges on Allwinner TV boxes by exploiting exposed ADB services enabled in production firmware.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-mfgm-xvxw-j43w

## What is CVE-2026-58378?

CVE-2026-58378 is a high-severity vulnerability in Allwinner H616, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Allwinner H616 TV Box TV98 has ADB enabled and exposed to the network on production. An attacker could request for ADB authorization and gain root level privileges if the victim allows access.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2026-58378 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58378 is a high-severity vulnerability in Allwinner H616, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58378 exists.

Affected product: Allwinner H616. 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-58378/ (Markdown: https://insights.sbomify.com/CVE-2026-58378/index.md)
```

## Sources

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

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