Google Android
In multiple locations, there is a possible out of bounds read and 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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- 16
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory source.android.com/docs/security/bulletin/2026/2026-03…
Timeline
Days relative to CVE publicationFirst public PoC 11 days before publication; not in CISA KEV. First PoC: aydin5245/cve-2026-0006 (created 19 Feb 2026, found by us: backfilled).
PoC repositories
Found on GitHub.3 PoCs · 1 informational · 1 suspicious or fake
PoCs 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| aydin5245/cve-2026-0006 | 19 Feb 2026 −11 d | 0 | PoC via PoC Index |
| mobilehackinglab/CVE-2026-0006-openapv-poc | 18 Apr 2026 +47 d | 16 | PoC |
| systemadminbd-official/zeroday-android-16 | 25 Jun 2026 +115 d | 0 | PoC via PoC Index
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Informational 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| okskaok3-hub/android-cve-2026-research | 11 Nov 2026 +253 d | 14 Nov 2026 | 1 | Informational · list |
Suspicious or fake 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| R3n3r0/CVE-2026-0006-step-2 | 19 Oct 2026 +231 d | 14 Nov 2026 | 0 | Suspicious · score 55
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. "Backfilled" means we found the repository more than 30 days after it was created. Do not run PoC code from unknown sources.