What is CVE-2026-0106?
In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
The record classifies CVE-2026-0106 under weakness classes CWE-787, CWE-125, CWE-119. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 247 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 9.3 — CRITICAL
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 1.6% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-02-05, last modified 2026-02-26
Is CVE-2026-0106 being exploited?
It currently carries a trending score of 5 in the Threadlinqs vulnerability feed.
Affected products and versions
- Google: Android
How to fix CVE-2026-0106
No vendor patch reference has been recorded for CVE-2026-0106 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-0106
1 tracked threat in the Threadlinqs corpus references CVE-2026-0106, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .