Unauthenticated RCE in Android framework (FrameDecoder) with CVSS 9.8 affecting billions of devices; widespread impact across Android ecosystem.
CVE-2026-58868
Android FrameDecoder heap overflow allows unauthenticated remote code execution.
Is CVE-2026-58868 being exploited?
Not confirmed. CVE-2026-58868 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-58868?
CVE-2026-58868 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58868?
Yes. A fix has been recorded for CVE-2026-58868. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-58868 affect?
CVE-2026-58868 affects Android OS (FrameDecoder / media component), Devices receiving Android Nov 2026 security bulletin (Pixel and OEM Android devices). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58868?
Apply Nov 2026 Android security updates immediately; restrict untrusted media handling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution via heap buffer overflow in FrameDecoder; attacker can run arbitrary code, persist malware, or crash devices.
Immediate action required
- affected17
- affected16-qpr2
- affected16
- affected15
- affected14
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- yes
- technical impact
- total
Assessed by CISA 3 Nov 2026 (SSVC 2.0.3).
timeline
- 2 Nov 2026Published
- 3 Nov 2026CISA SSVC assessment: exploitation none · same day later
- 5 Nov 2026CVE record last updated · 3 days later
- 6 Nov 2026Analysed by vulneraibility.com · same day later
- Linksource.android.com /docs/security/bulletin/2026/2026-11-01
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.