Skip to main content
← Vulnerabilities

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.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
Fixed in 14, 15, 16, 16-qpr2, 17
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.

Published
Last modified
Published
Not listed in CISA KEV
0/100 · provisional
Unclear
Fix
Fixed in 14, 15, 16, 16-qpr2, 17
None on Exploit-DB, Metasploit or GitHub

Summary

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

  • Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Google Android

    17, 16-qpr2, 16, 15, 14

Evidence 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-58868

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: source.android.com

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: source.android.com

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: source.android.com

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: cve.now feed data