Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-26426 Overview
CVE-2025-26426 is an input validation flaw in the Android BroadcastController.java component, specifically within the registerReceiverWithFeatureTraced method. The defect allows a local application to register for and receive broadcasts intended for the privileged android package. Because the system does not properly validate the receiver registration, a non-privileged app can intercept intents that should be scoped to the platform. Google published the fix in the Android Security Bulletin dated May 1, 2025, covering Android 13, 14, and 15.
Critical Impact
A local application can receive broadcasts targeted at the android system package, enabling local privilege escalation without user interaction or additional execution privileges.
Affected Products
- Google Android 13.0
- Google Android 14.0
- Google Android 15.0
Discovery Timeline
- 2025-09-04 - CVE CVE-2025-26426 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-26426
Vulnerability Analysis
The vulnerability resides in BroadcastController.java, part of the Android framework responsible for mediating broadcast delivery between applications and system components. The registerReceiverWithFeatureTraced method accepts receiver registration parameters without sufficiently validating the caller's authority to subscribe to broadcasts destined for the android package. As a result, a locally installed, unprivileged application can register a receiver and intercept system-scoped broadcasts.
The flaw is categorized under improper input validation [CWE-20]. Intercepted broadcasts may carry data or control signals that the receiving code trusts because it assumes delivery only to system components. By observing or acting on this content, a local attacker can elevate the privileges available to their application beyond its declared manifest permissions.
Root Cause
The root cause is missing or insufficient validation of the target package and caller identity during broadcast receiver registration. The framework fails to enforce that only components running as the system can bind to broadcasts addressed to the android package namespace.
Attack Vector
Exploitation requires local access through a malicious application installed on the device. No user interaction is required once the application is running. The attacker invokes registerReceiverWithFeatureTraced with crafted parameters to subscribe to privileged broadcasts, then processes incoming intents to achieve local privilege escalation. Verified exploitation details are limited to the vendor patches referenced in the Android Security Bulletin May 2025.
Detection Methods for CVE-2025-26426
Indicators of Compromise
- Installed applications that declare broadcast receivers targeting system-reserved actions without corresponding platform signatures.
- Unexpected registerReceiver or registerReceiverWithFeatureTraced calls originating from third-party packages in logcat traces.
- Applications that request broad IntentFilter subscriptions covering actions normally handled by android system components.
Detection Strategies
- Review installed APKs for manifest entries declaring broadcast receivers that overlap with system broadcasts.
- Audit mobile device management (MDM) telemetry for applications sideloaded onto Android 13, 14, or 15 devices not yet on the May 2025 patch level.
- Correlate anomalous process behavior with recent app installations on unpatched devices.
Monitoring Recommendations
- Enforce patch-level reporting via MDM and flag endpoints below the 2025-05-01 Android security patch level.
- Monitor the Google Play Protect status and installation sources on managed Android fleets.
- Collect and inspect logcat broadcast dispatch events on high-risk devices for registration anomalies.
How to Mitigate CVE-2025-26426
Immediate Actions Required
- Apply the Android security patch level 2025-05-01 or later on all Android 13, 14, and 15 devices.
- Restrict installation of untrusted applications and enforce installation only from vetted sources through MDM policy.
- Remove unused or unknown applications from managed devices until patches are confirmed.
Patch Information
Google addressed the issue in two framework commits referenced in the bulletin: Android framework commit 475f9914 and Android framework commit 99aae825. Device vendors ship these fixes under the 2025-05-01 patch level as documented in the Android Security Bulletin May 2025.
Workarounds
- No vendor-sanctioned workaround exists; apply the official patch as the primary mitigation.
- Where patching is delayed, limit application installation to the Google Play Store and disable sideloading via enterprise policy.
- Enroll devices in Google Play Protect and enforce compliance checks on patch level before granting access to corporate resources.
# Verify Android security patch level on a connected device
adb shell getprop ro.build.version.security_patch
# Expected output on patched devices: 2025-05-01 or later
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

