Secuno
ENNL
Book demo

CVE-2026-0106

Google Android buffer overflow

9.3 CRITICALEPSS 0.12%
  1. Published5 Feb 2026

Description

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.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Google Androidall versions

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-10910910.0
A vulnerability was detected in Wavlink WL-WN530BE1-A 251117. This vulnerability…
CVE-2026-962658.2
IBM Power Systems Firmware FW1060.00 through FW1060.81 is affected by a vulnerability…
CVE-2026-1089159.9
A vulnerability has been found in Edimax BR-6208AC 1.32. This affects an unknown part…
CVE-2026-1089149.9
A flaw has been found in Edimax BR-6208AC 1.32. Affected by this issue is some unknown…
CVE-2026-1088939.9
A vulnerability was identified in Linksys E1700 up to 1.0.0.4.003. This issue affects…
CVE-2026-10889210.0
A vulnerability was determined in Linksys E1700 1.0.0.4.003. This vulnerability affects…

Frequently asked

Is CVE-2026-0106 being actively exploited?

CVE-2026-0106 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.12%.

How severe is CVE-2026-0106?

CVE-2026-0106 has a CVSS 3.1 base score of 9.3, rated critical. EPSS estimates a 0.12% probability of exploitation.

Which products are affected by CVE-2026-0106?

Affected products include Google Android.

How do I fix CVE-2026-0106?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-0106 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.