5 hours ago
- A proposed change to ADB would restrict on-device ADB connections by binding ADBD only to the wifi interface, breaking loopback connections used by Shizuku and other tools.
- The change stems from a security vulnerability (CVE-2026-0073), but the maintainer's suggestion to limit to wlan0 would also affect legitimate uses like ADB over VPN or Ethernet.
- The author argues that on-device ADB cannot be exploited by malicious apps alone; it requires multiple human actions like enabling USB debugging and pairing.
- Instead of permanent prevention, the author recommends a persistent toggle that survives reboot and is hidden from third-party apps, allowing users to enable it at their own risk.
- Users with unique use cases are encouraged to provide constructive feedback on the IssueTracker, while low-quality comments should be avoided to prevent Google from locking the thread.