Skip to content
IoT

CVE-2026-58378

8.6
High
EPSS 0.44%Jul 10, 2026

ADB exposed on Allwinner H616 TV98 allows root-level takeover if user authorizes.

common questions

Is CVE-2026-58378 being exploited?

Not confirmed. CVE-2026-58378 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.

How severe is CVE-2026-58378?

CVE-2026-58378 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-58378?

Not known from our data. No patch reference has been recorded for CVE-2026-58378, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-58378 affect?

CVE-2026-58378 affects Allwinner H616 TV Box (TV98), Android TV boxes using Allwinner H616. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58378?

Disable ADB over network, block TCP/5555, isolate devices, apply vendor patch when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Allwinner H616 TV Box (TV98)Android TV boxes using Allwinner H616
impact

Network-exposed ADB can obtain root with user authorization, enabling remote command execution, persistence, data theft, and lateral movement.

action required

Immediate action required

affected versions
Allwinner H616
  • affected< *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free