/

CVE-2026-78745

Severity:

CRITICAL RISK

(9.8)

Improper Access Control (CWE-284) in HiDPT Android ADB

CVE-2026-78745

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

HiDPT Android devices using the affected Hi3751V350 or Hi3751V352E_DMO platforms may expose an Android Debug Bridge daemon with insufficient access controls. A remote attacker who can reach the daemon may be able to execute arbitrary code, potentially taking control of the device.

Affected context

The issue occurs in HiDPT Android environments where the Android Debug Bridge daemon (adbd) is reachable through a remote interface and does not sufficiently restrict access. Risk depends on network exposure, device configuration, authentication controls, and whether the daemon permits privileged debugging operations.

Exploit preconditions

  • Attack surface: Network-reachable Android Debug Bridge daemon
  • Required access: Remote network connectivity to the exposed ADB service; valid authentication may or may not be enforced depending on configuration
  • Trigger point: Interaction with the affected adbd service
  • Why exploitation is possible: Insufficient access-control enforcement may allow unauthorized remote interaction with a privileged debugging component, creating a path to arbitrary code execution

Why this happens

The vulnerability is an access-control failure in a privileged device-management interface. When adbd accepts remote interactions without adequately restricting who may connect or which operations are permitted, an untrusted remote party may reach capabilities intended only for authorized debugging. This behavior maps to CWE-284: Improper Access Control, because security-relevant operations are not reliably limited to authorized subjects.

Potential impact

  • An attacker may execute arbitrary code on the affected Android device
  • Device confidentiality, integrity, and availability could be compromised
  • Sensitive data could be accessed, modified, or removed
  • The device could be used to access connected networks or services
  • Malicious software or persistent unauthorized changes could be installed

General mitigation guidance

Mitigation generally focuses on reducing exposure of debugging interfaces and enforcing authorization at every privileged operation.

Common defensive patterns include:

  • Keeping ADB disabled in production and untrusted network environments
  • Binding debugging services only to trusted interfaces or isolated management networks
  • Requiring strong authentication and explicit user authorization for remote debugging
  • Applying least privilege to debugging daemons and related service accounts
  • Using network filtering, segmentation, and deny-by-default access policies
  • Monitoring and limiting administrative interfaces that can modify device state

These controls reduce attack surface even where the underlying component remains present.

How teams detect issues like this

Organizations commonly assess this class of issue through:

  • Network discovery for unexpectedly reachable ADB or debugging endpoints
  • Configuration reviews for enabled remote debugging and missing authorization controls
  • Static and source review checks for privileged service handlers lacking access validation
  • Device-policy enforcement that prohibits exposed debugging services in production
  • Runtime monitoring for unauthorized ADB connections, process creation, or service activity

Automated security scanners and configuration-compliance tools can help identify exposed management interfaces, but findings should be validated against deployment-specific access controls.

Sources

SourceLink
github.comgithub.com/n0c71v3x/CVE-2026-78745
weyontv.comweyontv.com/

Frequently asked

questions

Potentially. Exploitation requires network reachability to the affected ADB daemon and depends on whether authentication and other deployment controls restrict access.

Not necessarily. A remote attacker may be able to exploit the issue if the debugging service is exposed and insufficiently protected.

Disable ADB in production where it is not required, keep it off untrusted networks, and enforce strong authorization and least privilege when debugging must remain available.

Treat debugging and administrative interfaces as sensitive management surfaces, apply deny-by-default network policies, require explicit authorization, and continuously monitor for unexpected exposure.

Find out what's already
exploitable in your codebase.