Android May Restrict On-Device ADB, Affecting Shizuku and libadb
The proposed change would block localhost loopback connections, breaking on-device ADB tools like Shizuku and libadb, and other specialized development setups.
Reporting from 1 source: GIGAZINE.
Google is considering restricting the network interfaces ADB servers can bind to, which would block localhost loopback connections used for on-device ADB. The proposal follows the discovery of CVE-2026-0073, a vulnerability in wireless ADB authentication. Developer Kitsumed warns this would break tools like Shizuku and libadb.
Google is weighing a change to Android's ADB that would limit which network interfaces the ADB server can bind to. The proposal, discussed on Google's IssueTracker, suggests restricting binding to the Wi-Fi interface wlan0 only. That would block connections made through the localhost loopback address, which is how a device establishes an ADB connection to itself.
The request follows the discovery of CVE-2026-0073, a vulnerability that lets attackers bypass wireless ADB authentication entirely. A Google engineer, who is a core ADB maintainer, floated the wlan0 restriction as a countermeasure. Developer Kitsumed, who highlighted the discussion, argues the fix is too broad. It would also break VPN-based ADB, Ethernet-based ADB, and other specialized setups that rely on selecting a network interface.
Kitsumed notes the vulnerability cannot be exploited by a malicious app alone; it requires a human to perform multiple manual steps. He opposes restricting all options in response.
Synthesized by Yomimono from the 1 cited source below, including Japanese-language reporting where cited, then editorially reviewed before publishing.