dbcve.org
CWE-489Weakness · CWE-489

CVE-2026-58378

HIGH · 8.8 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Allwinner H616 TV Box TV98 ships with Android Debug Bridge (ADB) enabled and network-accessible in production. An attacker on the same network can connect to the exposed ADB service and request authorization; if the user approves the prompt, the attacker obtains a root shell.

MitigationDisable ADB in production firmware builds, or restrict ADB network binding to localhost only; if remote debugging is required, place behind a firewall and educate users to reject unauthorized ADB authorization requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if ADB network port is exposed
    Run 'adb devices' or scan port 5555 on the device IP using nmap: 'nmap -p 5555 <device-ip>'
    Affected if Port 5555 is open and accepting connections from the network (not filtered by firewall)
  2. Verify ADB responds to network connections
    Attempt to connect to the device over network: 'adb connect <device-ip>:5555'
    Affected if The connection succeeds or shows 'connected to <device-ip>:5555' without authentication barriers
  3. Confirm ADB is bound to network interface
    On the device (via existing access) or from network perspective, check if ADB is listening on 0.0.0.0:5555 rather than only 127.0.0.1:5555 using 'netstat -an | grep 5555' or similar
    Affected if ADB is listening on 0.0.0.0 or all interfaces (0.0.0.0:5555), making it reachable from external network sources
  4. Check if ADB daemon is running on the device
    If you have shell access, run 'getprop persist.sys.adb.enable' or check running processes for adbd
    Affected if ADB daemon is running and enabled on the device

If port 5555 is open and reachable from the network, and ADB accepts connections without local access requirements, the device is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable ADB in production firmware builds, or restrict ADB network binding to localhost only; if remote debugging is required, place behind a firewall and educate users to reject unauthorized ADB authorization requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58378 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data