谷歌正在评估限制Android Debug Bridge（ADB）守护进程访问范围的方案[1]。该措施将阻断本机回环地址（如127.0.0.1）的访问，仅允许通过Wi-Fi或USB连接进行ADB操作[1]。谷歌声称此举是为了应对CVE-2026-0073漏洞遗留风险，该漏洞曾导致无线ADB认证被绕过[1]。
这一限制措施将对多款系统定制工具造成实质性影响[1]。依赖设备端ADB的Termux终端模拟器和Shizuku提权等应用将难以正常使用[1]。同时，Android手机厂商已逐步收紧BootLoader解锁渠道，使传统ROOT方式变得困难[1]。这些举措共同推动Android系统的开放性进一步收缩，与iOS的差异逐渐缩小[1]。
Google is evaluating restrictions on the Android Debug Bridge (ADB) daemon's accessibility, planning to block connections through local loopback addresses in response to CVE-2026-0073 vulnerability risks [1]. Under the proposed changes, ADB access would be limited to Wi-Fi or USB connections only, with addresses like 127.0.0.1 being blocked [1]. The company has attributed this measure to mitigating the residual threat posed by the CVE-2026-0073 flaw, which previously allowed wireless ADB authentication to be bypassed [1].
The restrictions will significantly impact tools that rely on device-side ADB without requiring full root privileges, such as the Termux terminal emulator and Shizuku privilege escalation utilities, making them substantially more difficult to use [1]. This move represents a further tightening of Android's openness, as device manufacturers have already begun progressively restricting bootloader unlock channels, making traditional root modifications increasingly challenging [1]. The combined effect narrows the gap between Android and iOS in terms of user customization capabilities [1].
