CVE-2026-20417: Medium severity Google Android vulnerability
Published Feb 2, 2026
·Updated
In pcie, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10314946 / ALPS10340155; Issue ID: MSV-5154.
Affected Software
5 affected components
All of the following
Any of the following
Google Android=15.0
Google Android=16.0
Any of the following
MediaTek Mt6991
MediaTek Mt6993
MediaTek Mt8678
Event History
Feb 2, 2026
CVE Published
via MITRE·08:15 AM
Data Sourced
via MITRE·08:15 AM
DescriptionWeakness
Data Sourced
via NVD·09:15 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-20417?
CVE-2026-20417 has a high severity due to the potential for local privilege escalation.
2
How do I fix CVE-2026-20417?
To fix CVE-2026-20417, you should apply the patches ALPS10314946 or ALPS10340155 as recommended by the vendor.
3
Who is affected by CVE-2026-20417?
CVE-2026-20417 affects Google Android versions 15.0 and 16.0.
4
Is user interaction required for exploiting CVE-2026-20417?
No, user interaction is not needed for the exploitation of CVE-2026-20417.
5
Can CVE-2026-20417 lead to data breaches?
Yes, exploiting CVE-2026-20417 can lead to local escalation of privilege, potentially exposing sensitive data.