CVE-2025-26426
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-04

Last updated on: 2025-09-05

Assigner: Android (associated with Google Inc. or Open Handset Alliance)

Description
In BroadcastController.java of registerReceiverWithFeatureTraced, there is a possible way to receive broadcasts meant for the "android" package due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-04
Last Modified
2025-09-05
Generated
2026-05-07
AI Q&A
2025-09-04
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
google android 13.0
google android 14.0
google android 15.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs in the Android platform's BroadcastController.java, where improper input validation allows non-system user IDs to impersonate the 'android' package when registering broadcast receivers. This means that broadcasts intended only for the 'android' package could be received by unauthorized processes, leading to a local escalation of privilege without needing any additional execution privileges or user interaction. [1]


How can this vulnerability impact me? :

The vulnerability can allow unauthorized local processes to escalate their privileges by receiving broadcasts meant only for the 'android' system package. This could lead to unauthorized access to sensitive system broadcasts or actions, potentially compromising the security and integrity of the device without requiring user interaction. [1]


What immediate steps should I take to mitigate this vulnerability?

Apply the security patch released by the Android Open Source Project that enforces stricter validation of calling package identities in the ActivityManagerService component. This patch prevents non-system user IDs from using "android" as the calling package name, thereby mitigating the privilege escalation risk. Ensure your system is updated with the fix committed on March 12, 2025, as described in the Android frameworks/base repository. [1, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart