Google has released the June 2026 Android Security Bulletin, giving carriers and device makers a fresh set of patches to install.
Though Google puts out the Android security patches each month, the job of actually getting the fixes to end users falls on the telcos and/or device manufacturers themselves. Those partners vary in their ability to release the patches in a timely fashion.
The Android Security Bulletin contains details of security vulnerabilities affecting Android devices. Security patch levels of 05-06-2026 or later address all of these issues.
The most severe of these issues is a critical security vulnerability in the Framework component that could lead to remote escalation of privilege with no additional execution privileges needed.
The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are turned off for development purposes or if successfully bypassed.
Alongside the bulletin, Google have released a security update to Google devices through an over-the-air (OTA) update. The Google device firmware images have also been released to the Google Developer site. Security patch levels of June 2026 or later address all of these issues.
The tables below contains a list of security vulnerabilities, the Common Vulnerability and Exposures ID (CVE), the assessed severity, and whether or not Google devices are affected. The severity assessment is based on the effect that exploiting the vulnerability would possibly have on an affected device, assuming the platform and service mitigations are disabled for development purposes or if successfully bypassed.
Android and Google Service Mitigation’s
This is a summary of the mitigation’s provided by the Android security platform and service protections such as Google Play Protect. These capabilities reduce the likelihood that security vulnerabilities could be successfully exploited on Android.
- Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. All users are encouraged to update to the latest version of Android where possible.
- The Android security team actively monitors for abuse through Google Play Protect and warns users about Potentially Harmful Applications. Google Play Protect is enabled by default on devices with Google Mobile Services, and is especially important for users who install apps from outside of Google Play.
Terminology
You will find different types of vulnerabilities listed. Possible types include:
- RCE – Remote code execution
- EoP – Elevation of privilege
- ID – Information disclosure
- DoS – Denial of service
- N/A – Classification not available
01-06-2026 security patch level—Vulnerability details
Framework
The most severe vulnerability in this section could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2025-65018 | A-463998243 | EoP | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2025-64720 | A-463995203 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2025-22424 | A-350456241 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-22426 | A-365086157 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-48570 | A-376048041 | EoP | High | 14 |
| CVE-2025-48595 | A-430889718 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-48615 | A-433250316 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-48649 | A-339109116 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-48652 | A-452042097 | EoP | High | 15, 16, 16-qpr2 |
| CVE-2026-0009 | A-329631990 | EoP | High | 15, 16 |
| CVE-2026-0046 | A-443272513 | EoP | High | 14, 15, 16 |
| CVE-2026-0048 | A-463364410 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0055 | A-460779368 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0061 | A-452010556 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0076 | A-470115162 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0077 | A-467082881 | EoP | High | 16-qpr2 |
| CVE-2026-0078 | A-445418705 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0087 | A-483142784 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0089 | A-485397908 | EoP | High | 16-qpr2 |
| CVE-2026-0091 | A-438742644 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0100 | A-484973621 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-28577 | A-389950114 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-28580 | A-481967442 | EoP | High | 16, 16-qpr2 |
| CVE-2026-0016 | A-460933604 | ID | High | 16, 16-qpr2 |
| CVE-2026-0036 | A-405392600 | ID | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0056 | A-462431486 | ID | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-28586 | A-477935679 | ID | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-32348 | A-406880479 | DoS | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0018 | A-449392803 | DoS | High | 15, 16, 16-qpr2 |
| CVE-2026-0069 | A-480126173 | DoS | High | 14 |
| CVE-2026-0070 | A-438186009 | DoS | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-28578 | A-475228205 | DoS | High | 14, 15, 16, 16-qpr2 |
System
The most severe vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2026-0043 | A-453649377 | EoP | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0097 | A-446114623 | EoP | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-21352 | A-483693973 | EoP | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-21353 | A-483697751 | EoP | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2025-64505 | A-463980379 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0039 | A-470966846 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0040 | A-467994860 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0041 | A-467994310 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0042 | A-456471487 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0044 | A-449728942 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0051 | A-461790658 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0052 | A-467352655 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0080 | A-462431872 | DoS | Critical | 14, 15, 16, 16-qpr2 |
| CVE-2026-0059 | A-447536200 | RCE | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-26418 | A-351830787 | EoP | High | 14, 15 |
| CVE-2025-48581 | A-428945391 | EoP | High | 16 |
| CVE-2025-48612 | A-429417453 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0045 | A-380091558 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0075 | A-465133716 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0086 | A-476417007 | EoP | High | 16-qpr2 |
| CVE-2026-0088 | A-471127462 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0093 | A-473812391 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0094 | A-471173239 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0095 | A-484861632 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0096 | A-473005624 | EoP | High | 16, 16-qpr2 |
| CVE-2026-0098 | A-397217317 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0099 | A-385917501 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-28574 | A-496735702 | EoP | High | 16, 16-qpr2 |
| CVE-2025-48600 | A-435188844 | ID | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-48616 | A-438973280 | ID | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0050 | A-290364858 | ID | High | 15, 16, 16-qpr2 |
| CVE-2026-28581 | A-479515555 | ID | High | 14, 15, 16, 16-qpr2 |
| CVE-2025-48648 | A-396667508 | DoS | High | 14, 15, 16 |
| CVE-2026-0060 | A-459639258 | DoS | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0067 | A-470967228 | DoS | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0074 | A-468061774 | DoS | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0079 | A-470966318 | DoS | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-0085 | A-414389102 | DoS | High | 14, 15, 16, 16-qpr2 |
Google Play system updates
The following issues are included in Project Mainline components.
| Subcomponent | CVE |
|---|---|
| MediaProvider | CVE-2026-0009 |
| Documents UI | CVE-2026-0098 |
05-06-2026 security patch level—Vulnerability details
Kernel
The vulnerability in this section could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
| CVE | References | Type | Severity | Subcomponent |
|---|---|---|---|---|
| CVE-2025-40214 | A-463258435 Upstream kernel | EoP | High | Net |
Imagination Technologies
These vulnerabilities affect Imagination Technologies components and further details are available directly from Imagination Technologies. The severity assessment of these issues is provided directly by Imagination Technologies.
| CVE | References | Severity | Subcomponent |
|---|---|---|---|
| CVE-2026-21736 | A-382331631 | High | PowerVR-GPU |
| CVE-2026-22163 | A-477208444 | High | PowerVR-GPU |
| CVE-2026-22167 | A-492104691 | High | PowerVR-GPU |
MediaTek components
These vulnerabilities affect MediaTek components and further details are available directly from MediaTek. The severity assessment of these issues is provided directly by MediaTek.
| CVE | References | Severity | Subcomponent |
|---|---|---|---|
| CVE-2026-20432 | A-480646333 M-MOLY01406170 | High | Modem |
| CVE-2026-20433 | A-480745371 M-MOLY01088681 | High | Modem |
| CVE-2026-20447 | A-488940382 M-ALPS10724073 | High | geniezone |
| CVE-2026-20448 | A-488938763 M-ALPS10708513 | High | geniezone |
| CVE-2026-20453 | A-500172039 M-ALPS10886526 | High | geniezone |
| CVE-2026-20454 | A-500172040 M-ALPS10873936 | High | geniezone |
| CVE-2026-20455 | A-500171842 M-ALPS10873936 | High | geniezone |
| CVE-2026-20435 | A-493235107 M-ALPS10607099 | High | preloader |
| CVE-2026-20431 | A-480745369 M-MOLY01106496 | High | Modem |
| CVE-2026-20449 | A-488935936 M-MOLY01760138 | High | Modem |
| CVE-2026-20450 | A-488946597 M-MOLY01753620 | High | Modem |
Unisoc components
These vulnerabilities affect Unisoc components and further details are available directly from Unisoc. The severity assessment of these issues is provided directly by Unisoc.
| CVE | References | Severity | Subcomponent |
|---|---|---|---|
| CVE-2025-71251 | A-488917580 U-3192149 | High | Modem |
| CVE-2025-71252 | A-488896810 U-3192153 | High | Modem |
| CVE-2025-71253 | A-488917582 U-3192156 | High | Modem |
| CVE-2025-71254 | A-488926919 U-3192159 | High | Modem |
| CVE-2025-71255 | A-488928601 U-3192164 | High | Modem |
| CVE-2025-71256 | A-488928606 U-3217322 | High | Modem |
| CVE-2026-21538 | A-497208290 U-3281701 | High | Modem |
| CVE-2026-21539 | A-497585110 U-3281702 | High | Modem |
| CVE-2026-21540 | A-497585112 U-3281704 | High | Modem |
| CVE-2026-21541 | A-497208295 U-3281705 | High | Modem |
| CVE-2026-21542 | A-497208296 U-3281706 | High | Modem |
| CVE-2026-21543 | A-497585114 U-3281708 | High | Modem |
| CVE-2026-21544 | A-497585116 U-3281709 | High | Modem |
| CVE-2026-21545 | A-497208298 U-3281710 | High | Modem |
| CVE-2026-21546 | A-497587545 U-3281712 | High | Modem |
| CVE-2026-21547 | A-497587546 U-3281716 | High | Modem |
Qualcomm components
These vulnerabilities affect Qualcomm components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
| CVE | References | Severity | Subcomponent |
|---|---|---|---|
| CVE-2026-24085 | A-489081387 QC-CR#4389100 | High | Display |
| CVE-2026-24089 | A-480963667 QC-CR#4409502 | High | Display |
Qualcomm closed-source components
These vulnerabilities affect Qualcomm closed-source components and are described in further detail in the appropriate Qualcomm security bulletin or security alert. The severity assessment of these issues is provided directly by Qualcomm.
| CVE | References | Severity | Subcomponent |
|---|---|---|---|
| CVE-2025-47392 | A-449732037 | Critical | Closed-source component |
| CVE-2026-25276 | A-500022090 | Critical | Closed-source component |
| CVE-2026-25277 | A-500022443 | Critical | Closed-source component |
| CVE-2025-47384 | A-482066737 | High | Closed-source component |
| CVE-2025-47400 | A-490088971 | High | Closed-source component |
| CVE-2025-47401 | A-457748569 | High | Closed-source component |
| CVE-2025-47403 | A-457748033 | High | Closed-source component |
| CVE-2025-59604 | A-465463345 | High | Closed-source component |
| CVE-2025-59605 | A-465462444 | High | Closed-source component |
| CVE-2025-59606 | A-465461683 | High | Closed-source component |
| CVE-2026-21367 | A-473524385 | High | Closed-source component |
| CVE-2026-21372 | A-490089371 | High | Closed-source component |
| CVE-2026-21373 | A-490089294 | High | Closed-source component |
| CVE-2026-21374 | A-490088523 | High | Closed-source component |
| CVE-2026-21375 | A-490088656 | High | Closed-source component |
| CVE-2026-21376 | A-490089071 | High | Closed-source component |
| CVE-2026-21378 | A-490088320 | High | Closed-source component |
| CVE-2026-21380 | A-490088402 | High | Closed-source component |
| CVE-2026-21381 | A-473524555 | High | Closed-source component |
Full details of the June 2026 Android Security Bulletin are available here.
