In multiple locations, there is a possible way to trick a user into accepting a permission due to a tapjacking/overlay attack.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 14, 15
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 14, 15.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 14, 15
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
This vulnerability affects an Android system component that handles app permission prompts, allowing a malicious app to hide or overlay those prompts. As a result, a user could be tricked into granting a permission they did not intend to, which could allow a local app to gain elevated privileges.
Read the original description
In multiple locations, there is a possible way to trick a user into accepting a permission due to a tapjacking/overlay attack. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
What to do
Upgrade to a fixed version: 14, 15.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
15, 14
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-26433
What does this mean?
The advisory describes a possible way to trick a user into accepting a permission through a tapjacking or overlay attack in multiple locations in Android. The advisory classifies the impact as elevation of privilege (EoP) on the affected device.Source: source.android.com
Am I affected, and how do I check?
The advisory lists Google Android as the product but gives no affected version range or specific setup. To check a device, open Settings > About phone and read the Android version and security patch level, then compare them with the advisory's listing.Source: source.android.com
What should I do about it?
The advisory lists fixes for Android 14 and 15, so install the available update for your device's Android version. No workaround is listed in the facts.Source: source.android.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data