- Google said its most severe Android bulletin issue could lead to remote code execution without additional privileges or user interaction.
- Google said CVE-2026-58868 affects Android 14 through 17.
- Android security patch levels dated 2026-11-05 or later address all November bulletin issues.
Google has published its Android security bulletin and patched a critical Framework vulnerability that could lead to remote code execution without additional privileges or user interaction.
The issue affects Android versions 14 through 17, while phone makers and carriers deliver the fix on their own schedules. Google’s records do not say how an attacker would reach the vulnerable code.
Android 12 and 13 are not listed as affected, but Google’s records do not say whether those versions contain the flaw. As of November 4, Google’s bulletin did not report attacks exploiting its flaws, and CISA’s catalog did not list the issue as of its November 3 update.
On this page
CVE-2026-58868 is a possible heap buffer overflow
Google said the flaw is a possible out-of-bounds write caused by a heap buffer overflow in the onOutputReceived function of FrameDecoder.cpp.
The company said its Critical rating assumes Android and Google service protections are turned off or bypassed. Neither the bulletin nor the flaw’s CVE record says how an attacker would reach the vulnerable code.
Android uses two November security patch levels
Google said a 2026-11-01 or later security update covers CVE-2026-58868 and other flaws in the Framework, System and Android runtime components. A 2026-11-01 patch level addresses all issues associated with that patch level.
The company said the two patch levels give Android partners flexibility to fix a subset of vulnerabilities shared across devices more quickly. Phones receive the relevant updates according to phone-maker and carrier schedules.
Google said Android security patch levels dated 2026-11-05 or later address all November bulletin issues. It also said corresponding source-code patches would be released to the Android Open Source Project repository within 48 hours after the bulletin’s initial publication.
| Patch level | Coverage |
|---|---|
| 2026-11-01 or later | Covers CVE-2026-58868 and the other flaws in the Framework, System and Android runtime components; addresses all issues associated with that patch level. |
| 2026-11-05 or later | Addresses all November bulletin issues. |
What to do now
- Update to the latest version of Android where possible.
FAQ
What is CVE-2026-58868?
Google said it is a possible out-of-bounds write caused by a heap buffer overflow in the onOutputReceived function of FrameDecoder.cpp. The issue could lead to remote code execution without additional privileges or user interaction.
Which Android versions are affected by CVE-2026-58868?
Google said the flaw affects Android 14 through 17. Android 12 and 13 are not listed as affected, but Google’s records do not say whether they contain it.
Has CVE-2026-58868 been exploited?
As of November 4, Google’s bulletin did not report attacks exploiting its flaws. CISA’s Known Exploited Vulnerabilities catalog also did not list the issue as of its November 3 update.
How do I fix CVE-2026-58868 on Android?
Google said Android security patch levels dated 2026-11-05 or later address all November bulletin issues. It also said a 2026-11-01 or later security patch level covers CVE-2026-58868, subject to phone-maker and carrier schedules.
Sources
How we checked this story
| Claim | Source | Status |
|---|---|---|
| Google said the most severe Android bulletin issue could lead to remote code execution without additional privileges or user interaction. | Confirmed | |
| Google said Android security patch levels dated 2026-11-05 or later address all November bulletin issues. | Confirmed | |
| Neither Google’s bulletin nor the CVE record says how an attacker would reach the vulnerable code. | Google, via The Hacker News | Attributed |
| As of November 4, Google’s bulletin did not report attacks exploiting its flaws. | Google, via The Hacker News | Attributed |
| The flaw is not listed in CISA’s Known Exploited Vulnerabilities catalog as of its November 3 update. | CISA, via The Hacker News | Attributed |
| Android 12 and 13 are not listed as affected, but Google’s records do not say whether they contain the flaw. | Google, via The Hacker News | Attributed |
| Google said partners receive notice of all Android issues at least one month before bulletin publication. | Confirmed | |
| Google said corresponding source-code patches would be released to AOSP within 48 hours after the bulletin’s initial publication. | Confirmed | |
| Google said Android security patch levels dated 2026-11-01 or later address all issues associated with that patch level. | Confirmed | |
| Google said Android partners may fix a subset of vulnerabilities sooner using the two patch levels. | Confirmed | |
| Google encourages Android partners to fix all issues in the bulletin and use the latest security patch level. | Confirmed |
Could not verify
- Whether CVE-2026-58868 was exploited in the wild is not established.
- How many devices are affected is not established.
- How an attacker would reach the vulnerable code is not established.
- Whether Android 12 and 13 contain the flaw is not established.



