Google Is Weighing Binding ADB to wlan0 Only — Which Would Break Termux, Shizuku and On-Device Android Development
An ADB core maintainer proposed in Google IssueTracker #526109803 restricting adbd to bind only the WiFi interface (`wlan0`), eliminating loopback connections on 127.0.0.1, following CVE-2026-0073 — a bypass of Wireless ADB authentication. If shipped, it would break on-device developer workflows built on Termux, plus Shizuku, libadb-android, App Manager and ShizuCallRecorder, along with ADB over VPN and Ethernet, and accessibility tooling that depends on local ADB. The analysis (published July 20, last edited July 24, 336 points on HN July 25) is explicit that this is not an official Google announcement and reflects an ongoing discussion, not a decision — treat it as an early warning to watch the tracker, not a shipped change. Single-source and pre-decisional, so weighted low.
↳ Follow the thread