Google is considering restricting on-device Android Debug Bridge (ADB) connections to improve security, a move that could inadvertently disable popular power-user tools like Shizuku and various developer applications.

Key Points

• Google developers are discussing limiting ADB daemon (ADBD) connections to the Wi-Fi interface (wlan0) to mitigate potential privilege escalation exploits.
• The proposed change would effectively block "on-device" ADB, where developers use terminal emulators to run ADB commands locally via the loopback address (127.0.0.1).
• Popular open-source projects, including Shizuku, aShell, and various call recording utilities, rely on this local loopback connection to function.
• Security concerns stem from CVE-2026-0073, which previously allowed attackers to bypass Wireless ADB authentication.
• Critics argue that malicious exploitation of on-device ADB requires significant manual user intervention, making a total ban unnecessary and overly restrictive for power users.

Why it Matters

Restricting on-device ADB would disrupt a niche but vital ecosystem of tools that allow users to customize their devices and manage permissions without a secondary computer. This change highlights the ongoing tension between Google’s efforts to harden Android security and the needs of developers who rely on advanced system-level access.