Android 17 Advanced Protection Mode Restricts Accessibility API Abuse
Vulnerability Disclosure · 4 sources · Updated 5mo ago · First seen Mar 16, 2026

Google added a new safeguard in Android 17 Beta 2 that blocks apps not classified as genuine accessibility tools from using the Accessibility Services API when Android Advanced Protection Mode (AAPM) is enabled. The change is intended to reduce a long-standing abuse path used by Android malware, which has leveraged accessibility permissions to read screen content, capture keystrokes, click through prompts, grant permissions, install additional payloads, and steal sensitive data including banking credentials. Under the new model, only verified accessibility apps marked with isAccessibilityTool="true" can retain this level of access.
The restriction expands AAPM’s opt-in hardened security posture, which already includes controls such as blocking installs from unknown sources, limiting USB data access, and requiring Google Play Protect scanning. Google said developers can use the AdvancedProtectionManager API to detect whether the mode is active and adjust application behavior accordingly. The policy also narrows which app categories qualify as accessibility tools, with examples including screen readers, switch-based input, voice input, and Braille access software, while categories such as antivirus tools, automation apps, assistants, monitoring apps, cleaners, password managers, and launchers are not treated as accessibility tools for this exemption.

