CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVE-2026-58868 google android: Out-of-bounds Write
Critical (9.8) in google android. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
- EPSS
- 0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-787 Out-of-bounds Write
- Published
- Modified
- NVD analysis
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-58868 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-58868?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-58868?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-58868 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-58868)
HTML:
<a href="https://cve.bz/cve/CVE-2026-58868"><img src="https://cve.bz/cve/badge/CVE-2026-58868.svg" alt="CVE-2026-58868"></a>
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| google:android | 14.0 |
| google:android | 15.0 |
| google:android | 16.0 |
| google:android | 16.0:qpr2 |
| google:android | 17.0 |
Fix and patched versions
- Patch: https://source.android.com/docs/security/bulletin/2026/2026-11-01
- Vendor advisory: https://source.android.com/docs/security/bulletin/2026/2026-11-01
GitHub PoC (unverified)
Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
- redfishrouge/CVE-2026-58868-PoC 2 stars, Shell, created
- probear0001/CVE-2026-58868 1 star, created
Original write up for CVE-2026-58868 Android critical severity cve
History
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.