Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-0106

9.3 · CRITICAL

In vpu_mmap of vpu_ioctl, there is a possible arbitrary address mmap due to a missing bounds check.

Published Feb 5, 2026CWE-119EPSS 0.12%

Overview

CVE-2026-0106 is a critical-severity vulnerability. It was published on February 5, 2026 and has a CVSS 3.1 base score of 9.3 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.3, rated CRITICAL. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refsource.android.com/docs/security/bulletin/pixel/2026/2026-02-01

How CyberStrike helps

Frequently asked questions

What is CVE-2026-0106?

CVE-2026-0106 is a critical-severity vulnerability. It was published on February 5, 2026 and has a CVSS 3.1 base score of 9.3 (CRITICAL).

How severe is CVE-2026-0106?

This vulnerability has a CVSS 3.1 base score of 9.3, rated CRITICAL. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-0106?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-0106?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-0106 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999