Early warning: a core ADB maintainer on Google Issue Tracker mentioned restricting on‑device ADB to guard against “bad actors”. The change, tied to a recent CVE‑2026‑0073 exploit, would let developers choose which interface ADBD listens on, instead of exposing the daemon on all connected networks. While this could reduce attack surface, it would also break popular on‑device workflows used by projects such as Shizuku and libadb that rely on loopback connections. The maintainer suggested binding to the Wi‑Fi interface (wlan0), but that would disable loopback, VPN, Ethernet, and many niche setups. The author, Kitsumed, a Shizuku‑based app developer, notes that on‑device ADB is often a legitimate tool for power users and accessibility, and that a malicious app alone cannot establish it without human interaction. He urges the community to provide constructive feedback or simply upvote relevant issues to influence the outcome.

Developers can support the discussion by adding detailed use‑case explanations and technical solutions in the tracker, or simply by clicking the +1 button to signal impact. Spamming the thread is discouraged, as it may cause the issue to be locked or ignored. If the restriction goes ahead, developers will need to adjust their tooling, perhaps by enabling VPN or using direct USB debugging, to regain the convenience previously offered.