This Android Security Bulletin contains details of security vulnerabilities that affect Android devices. Security patch levels of 2026-11-05 or later address all of these issues. To learn how to check a device's security patch level, see Check and update your Android version.
Within 48 hours after the initial publication of this bulletin, we will release the corresponding source code patches to the Android Open Source Project (AOSP) repository. We will then revise this bulletin with the AOSP links.
The most severe of these issues is a critical security vulnerability in the Framework component that could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. 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.
For more details on the Android security platform protections and Google Play Protect, which improve the security of the Android platform, refer to the Android and Google Play Protect mitigations section.
We notify our Android partners of all issues at least a month before publishing the bulletin.
Android and Google service mitigations
This is a summary of the mitigations 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. We encourage all users 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.
2026-11-01 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2026-11-01 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID. Devices with Android 10 and later may receive security updates as well as Google Play system updates.
Android runtime
The most severe vulnerability in this section could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2026-58988 | A-269456968 | ID | High | 14, 15, 16, 16-qpr2, 17 |
Framework
The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2026-58868 | A-486464711 | RCE | Critical | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58857 | A-503553199 | RCE | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2025-22424 | A-350456241 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2025-22426 | A-365086157 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2025-22442 | A-382064697 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2025-26433 | A-385347977 | EoP | High | 14, 15 |
| CVE-2026-28588 | A-475232460 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-28597 | A-262884935 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-28645 | A-466379326 | EoP | High | 15, 16, 16-qpr2, 17 |
| CVE-2026-45514 | A-465446148 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-49923 | A-498857374 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55257 | A-472968114 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55271 | A-499298430 | EoP | High | 17 |
| CVE-2026-55287 | A-472955222 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58836 | A-349318333 | EoP | High | 16, 16-qpr2, 17 |
| CVE-2026-58837 | A-525133623 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58853 | A-503542266 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58866 | A-494816520 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58886 | A-527035500 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58934 | A-527038637 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58944 | A-527036864 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58946 | A-527034642 | EoP | High | 16, 16-qpr2, 17 |
| CVE-2026-58957 | A-500368515 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58961 | A-527039128 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58962 | A-527035781 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58965 | A-514861143 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58966 | A-511632970 | EoP | High | 16-qpr2, 17 |
| CVE-2026-58970 | A-478861451 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58974 | A-527036176 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58975 | A-506176085 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58978 | A-459460815 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58979 | A-527038421 | EoP | High | 17 |
| CVE-2026-58986 | A-514738229 | EoP | High | 16, 16-qpr2, 17 |
| CVE-2026-58989 | A-429182079 | EoP | High | 15, 16, 16-qpr2 |
| CVE-2026-58995 | A-505748392 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59004 | A-472701802 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59014 | A-505573349 | EoP | High | 16, 16-qpr2, 17 |
| CVE-2025-22436 | A-277076451 | ID | High | 14, 15 |
| CVE-2026-28586 | A-477935679 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-28621 | A-356604577 | ID | High | 14, 15, 16 |
| CVE-2026-49935 | A-495409704 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55264 | A-498162425 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58838 | A-482947423 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58933 | A-501467247 | ID | High | 16, 16-qpr2, 17 |
| CVE-2026-58951 | A-527037031 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58969 | A-514738573 | ID | High | 16-qpr2, 17 |
| CVE-2026-58971 | A-511027559 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58997 | A-513648011 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59002 | A-519884370 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59006 | A-493560718 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59011 | A-484925508 | ID | High | 16, 16-qpr2, 17 |
| CVE-2026-59015 | A-497659915 | ID | High | 15, 16, 16-qpr2, 17 |
| CVE-2026-59022 | A-517377899 | ID | High | 15, 16, 16-qpr2, 17 |
| CVE-2026-28643 | A-495646742 | DoS | High | 16, 16-qpr2, 17 |
| CVE-2026-49924 | A-451602444 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55272 | A-492093013 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58817 | A-429417238 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58875 | A-515038894 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58937 | A-464276781 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58938 | A-503554506 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58949 | A-503551664 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59008 | A-281543351 | DoS | High | 16-qpr2, 17 |
| CVE-2026-59020 | A-515039372 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59021 | A-515039631 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59031 | A-514737201 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
System
The most severe vulnerability in this section could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
| CVE | References | Type | Severity | Updated AOSP versions |
|---|---|---|---|---|
| CVE-2026-58876 | A-503543341 | RCE | Critical | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58936 | A-496614216 | RCE | Critical | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55275 | A-522376559 | EoP | Critical | 16, 16-qpr2, 17 |
| CVE-2026-55283 | A-522375782 | EoP | Critical | 16, 16-qpr2, 17 |
| CVE-2026-58984 | A-514731794 | EoP | Critical | 15, 16, 16-qpr2, 17 |
| CVE-2026-58814 | A-517378147 | DoS | Critical | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58882 | A-517376969 | DoS | Critical | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-0053 | A-368376056 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-28580 | A-481967442 | EoP | High | 16, 16-qpr2, 17 |
| CVE-2026-28665 | A-488559440 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-45522 | A-482024712 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-49922 | A-504612754 | EoP | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-49934 | A-508585261 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55261 | A-503545851 | EoP | High | 16, 16-qpr2, 17 |
| CVE-2026-55262 | A-505067993 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55263 | A-472976054 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55289 | A-505203996 | EoP | High | 17 |
| CVE-2026-58867 | A-515051007 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58871 | A-511543870 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58879 | A-517593332 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58884 | A-515051745 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58885 | A-517377188 | EoP | High | 17 |
| CVE-2026-58943 | A-313418699 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58956 | A-461507723 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58964 | A-515712425 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58968 | A-503554745 | EoP | High | 16, 16-qpr2, 17 |
| CVE-2026-58994 | A-532588581 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59000 | A-517378646 | EoP | High | 16-qpr2, 17 |
| CVE-2026-59005 | A-517376786 | EoP | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59016 | A-546680461 | EoP | High | 17 |
| CVE-2026-59028 | A-522373825 | EoP | High | 15, 16, 16-qpr2, 17 |
| CVE-2025-48600 | A-435188844 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-28632 | A-444443479 | ID | High | 14, 15, 16, 16-qpr2 |
| CVE-2026-49912 | A-478725173 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-49931 | A-490916793 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-55292 | A-503550880 | ID | High | 16, 16-qpr2, 17 |
| CVE-2026-58821 | A-463363325 | ID | High | 16, 16-qpr2, 17 |
| CVE-2026-58870 | A-515047710 | ID | High | 15, 16, 16-qpr2, 17 |
| CVE-2026-58877 | A-500705928 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58945 | A-465140520 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58953 | A-478124606 | ID | High | 16, 16-qpr2, 17 |
| CVE-2026-58976 | A-496454250 | ID | High | 15, 16, 16-qpr2, 17 |
| CVE-2026-58990 | A-511263142 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59001 | A-517376998 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59003 | A-515391495 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59007 | A-514742326 | ID | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-59012 | A-527424853 | ID | High | 14 |
| CVE-2026-55288 | A-517377278 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58883 | A-517377202 | DoS | High | 16-qpr2, 17 |
| CVE-2026-58955 | A-503434084 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58963 | A-517377034 | DoS | High | 14, 15, 16, 16-qpr2, 17 |
| CVE-2026-58985 | A-514745329 | DoS | High | 16-qpr2, 17 |
| CVE-2026-59010 | A-509578318 | DoS | High | 14, 15, 16, 16-qpr2 |
Google Play system updates
The following issues are included in Project Mainline components.
| Subcomponent | CVE |
|---|---|
| Media Codecs | CVE-2026-58933 |
| Media Codecs, Media Framework components | CVE-2026-58938 |
| MediaProvider | CVE-2026-59011, CVE-2026-59022 |
| Media Codecs | CVE-2026-58876, CVE-2026-58953, CVE-2026-58968 |
| MediaProvider | CVE-2026-58821 |
| Profiling | CVE-2026-59016 |
| Telephonycore | CVE-2026-49922, CVE-2026-49934, CVE-2026-55289, CVE-2026-58883 |
| WiFi | CVE-2026-58867, CVE-2026-58870, CVE-2026-58877, CVE-2026-58884 |
2026-11-05 security patch level vulnerability details
In the sections below, we provide details for each of the security vulnerabilities that apply to the 2026-11-05 patch level. Vulnerabilities are grouped under the component they affect. Issues are described in the tables below and include CVE ID, associated references, type of vulnerability, severity, and updated AOSP versions (where applicable). When available, we link the public change that addressed the issue to the bug ID, like the AOSP change list. When multiple changes relate to a single bug, additional references are linked to numbers following the bug ID.
Kernel components
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 | Subcomponent |
|---|---|---|---|---|
| CVE-2026-53256 | A-508702285 Upstream kernel [2] |
EoP | Critical | Bluetooth |
| CVE-2026-59044 | A-508702141 Upstream kernel |
EoP | Critical | pKVM |
| CVE-2026-59045 | A-512428751 Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] |
EoP | Critical | pKVM |
| CVE-2026-80604 | A-517387820 Upstream kernel [2] |
EoP | Critical | HID |
| CVE-2026-89774 | A-508702364 Upstream kernel [2] [3] [4] |
EoP | Critical | Bluetooth |
| CVE-2026-59048 | A-512433296 Upstream kernel [2] |
ID | Critical | pKVM |
| CVE-2025-38627 | A-499041514 Upstream kernel [2] [3] [4] |
EoP | High | Flash-Friendly File System |
| CVE-2026-23240 | A-500321403 Upstream kernel |
EoP | High | Transport Layer Security |
| CVE-2026-31533 | A-504553976 Upstream kernel [2] |
EoP | High | TLS |
| CVE-2026-43284 | A-510777270 Upstream kernel [2] [3] [4] |
EoP | High | Networking |
| CVE-2026-43499 | A-496407345 Upstream kernel [2] [3] [4] |
EoP | High | Locking |
| CVE-2026-46242 | A-509838226 Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] |
EoP | High | Fs |
| CVE-2026-58824 | A-503395542 Upstream kernel [2] |
EoP | High | Protected Kernel-Based Virtual Machine |
| CVE-2026-58825 | A-499361237 Upstream kernel [2] |
EoP | High | Direct Memory Access Buffer |
| CVE-2026-58826 | A-498850457 Upstream kernel [2] [3] [4] |
EoP | High | Direct Memory Access Buffer |
| CVE-2026-58827 | A-499359964 Upstream kernel [2] |
EoP | High | Direct Memory Access Buffer |
| CVE-2026-58828 | A-496996374 Upstream kernel [2] [3] [4] |
EoP | High | Direct Memory Access Buffer |
| CVE-2026-58829 | A-498749316 Upstream kernel [2] |
EoP | High | FUSE |
| CVE-2026-58844 | A-503384798 Upstream kernel [2] [3] [4] [5] [6] [7] [8] [9] |
EoP | High | Protected Kernel-Based Virtual Machine |
| CVE-2026-58845 | A-498369302 Upstream kernel [2] |
EoP | High | Memory Management |
| CVE-2026-58847 | A-503385812 Upstream kernel |
EoP | High | Protected Kernel-Based Virtual Machine |
| CVE-2026-58942 | A-498371235 Upstream kernel [2] |
EoP | High | Memory Management |
| CVE-2026-59042 | A-503427706 Upstream kernel [2] |
EoP | High | pKVM |
| CVE-2026-59043 | A-503379315 Upstream kernel |
EoP | High | pKVM |
| CVE-2026-64011 | A-500030631 Upstream kernel [2] [3] [4] |
EoP | High | NFC |
| CVE-2026-64427 | A-489036052 Upstream kernel [2] [3] [4] [5] [6] |
EoP | High | Human Interface Device |
| CVE-2026-64560 | A-533808379 Upstream kernel [2] |
EoP | High | Kernel |
| CVE-2026-46232 | A-508701836 Upstream kernel [2] [3] [4] |
ID | High | HID |
| CVE-2026-23184 | A-468680876 Upstream kernel |
DoS | High | Binder |
| CVE-2026-59046 | A-508541359 Upstream kernel [2] |
DoS | High | pKVM |
| CVE-2026-59047 | A-503393436 Upstream kernel |
DoS | High | pKVM |
Arm components
These vulnerabilities affect Arm components and further details are available directly from Arm. The severity assessment of these issues is provided directly by Arm.
| CVE | References | Severity | Subcomponent | |
|---|---|---|---|---|
| CVE-2025-0647 |
A-476123052 * | High | CPU | |
| CVE-2026-9040 |
A-527031175 * | High | Mali | |
| CVE-2026-11891 |
A-527047523 * | High | Mali |
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-22165 |
A-489972410 * | High | PowerVR-GPU | |
| CVE-2026-65587 |
A-542541019 * | High | PowerVR-GPU | |
| CVE-2026-15466 |
A-531596246 * | High | PowerVR-GPU | |
| CVE-2026-16280 |
A-508272003 * | High | PowerVR-GPU | |
| CVE-2026-18629 |
A-524406423 * | High | PowerVR-GPU | |
| CVE-2026-19199 |
A-545553862 * | High | PowerVR-GPU | |
| CVE-2026-41155 |
A-499033076 * | High | PowerVR-GPU | |
| CVE-2026-45199 |
A-520408029 * | High | PowerVR-GPU | |
| CVE-2026-45201 |
A-530643753 * | High | PowerVR-GPU | |
| CVE-2026-45204 |
A-524198442 * | High | PowerVR-GPU | |
| CVE-2026-65586 |
A-508237844 * | High | PowerVR-GPU | |
| CVE-2026-74912 |
A-545799269 * | 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-20499 |
A-528209854 M-MOLY01857954 * |
Critical | Modem | |
| CVE-2026-20519 |
A-541967271 M-MOLY01778993 * |
Critical | Modem | |
| CVE-2026-20520 |
A-541967273 M-MOLY01778988 * |
Critical | Modem | |
| CVE-2026-20545 |
A-557043202 M-MOLY01774038 * M-MOLY01879158 * |
Critical | Modem | |
| CVE-2026-20546 |
A-557043203 M-MOLY01876654 * M-MOLY01774038 * |
Critical | Modem | |
| CVE-2026-20547 |
A-557043204 M-MOLY01874018 * M-MOLY01774038 * |
Critical | Modem | |
| CVE-2026-20548 |
A-557043205 M-MOLY01872867 * M-MOLY01774038 * |
Critical | Modem | |
| CVE-2026-20549 |
A-557051694 M-MOLY01775865 * |
Critical | Modem | |
| CVE-2026-20521 |
A-541960865 M-ALPS11375674 * |
High | Video HAL | |
| CVE-2026-20522 |
A-541965929 M-ALPS11249050 * |
High | neuropilot | |
| CVE-2026-20523 |
A-541965931 M-ALPS11249062 * |
High | neuropilot | |
| CVE-2026-20524 |
A-541960867 M-ALPS11249004 * |
High | apu | |
| CVE-2026-20526 |
A-541967277 M-MOLY01898195 * |
High | Modem | |
| CVE-2026-20553 |
A-557060234 M-ALPS11468968 * |
High | DA | |
| CVE-2026-20554 |
A-557065686 M-MOLY01911177 * |
High | Modem | |
| CVE-2026-20556 |
A-557051697 M-MOLY01876662 * |
High | Modem | |
| CVE-2026-20557 |
A-557051698 M-MOLY01877236 * |
High | Modem | |
| CVE-2026-20558 |
A-557065687 M-ALPS11365070 * |
High | GPU pdma | |
| CVE-2026-20559 |
A-557051699 M-ALPS11365081 * |
High | GPU pdma | |
| CVE-2026-20565 |
A-557060238 M-MOLY01778991 * |
High | Modem | |
| CVE-2026-20586 |
A-546432839 M-ALPS11383899 * |
High | vdec | |
| CVE-2026-20589 |
A-546432840 M-ALPS11383899 * |
High | vdec | |
| CVE-2026-20525 |
A-541960869 M-MOLY01870473 * M-MOLY00814393 * |
High | Modem | |
| CVE-2026-20527 |
A-541967278 M-MOLY01864925 * M-MOLY01210562 * |
High | Modem | |
| CVE-2026-20555 |
A-557051696 M-MOLY01876664 * |
High | Modem | |
| CVE-2026-20560 |
A-557065688 M-MOLY01870543 * |
High | Modem | |
| CVE-2026-20561 |
A-557060235 M-MOLY01750090 * |
High | Modem | |
| CVE-2026-20562 |
A-557060236 M-MOLY01775984 * |
High | Modem | |
| CVE-2026-20563 |
A-557051700 M-MOLY01777997 * |
High | Modem | |
| CVE-2026-20564 |
A-557060237 M-MOLY01780439 * |
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-2026-66086 |
A-539342791 U-3406715 * |
High | Modem | |
| CVE-2026-79405 |
A-553145530 U-3457076 * |
High | Modem | |
| CVE-2026-80335 |
A-553139427 U-3502927 * |
High | uboot | |
| CVE-2026-80336 |
A-553139428 U-3502931 * |
High | uboot |
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-25291 |
A-532129554 QC-CR#4403192 |
High | Security | |
| CVE-2026-25301 |
A-542224505 QC-CR#4424931 |
High | Security | |
| CVE-2026-57537 |
A-532130350 QC-CR#4252624 |
High | Security | |
| CVE-2026-57545 |
A-532130662 QC-CR#4478735 |
High | Security | |
| CVE-2026-57548 |
A-542224386 QC-CR#4488190 [2] |
High | Security | |
| CVE-2026-57549 |
A-542225265 QC-CR#4491000 |
High | Security | |
| CVE-2026-57554 |
A-532129432 QC-CR#4499506 [2] [3] |
High | Security | |
| CVE-2026-66113 |
A-542225657 QC-CR#4531192 |
High | Security | |
| CVE-2026-66114 |
A-542225732 QC-CR#4532353 |
High | Security |
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-2026-25285 |
A-509524400 * | Critical | Closed-source component | |
| CVE-2026-6726 |
A-542224547 * | High | Closed-source component | |
| CVE-2026-25286 |
A-509524956 * | High | Closed-source component | |
| CVE-2026-25287 |
A-509525554 * | High | Closed-source component | |
| CVE-2026-25302 |
A-532130009 * | High | Closed-source component | |
| CVE-2026-57546 |
A-532130527 * | High | Closed-source component | |
| CVE-2026-57547 |
A-532130053 * | High | Closed-source component | |
| CVE-2026-65076 |
A-542225318 * | High | Closed-source component |
Common questions and answers
This section answers common questions that may occur after reading this bulletin.
1. How do I determine if my device is updated to address these issues?
To learn how to check a device's security patch level, see Check and update your Android version.
- Security patch levels of 2026-11-01 or later address all issues associated with the 2026-11-01 security patch level.
- Security patch levels of 2026-11-05 or later address all issues associated with the 2026-11-05 security patch level and all previous patch levels.
Device manufacturers that include these updates should set the patch string level to:
- [ro.build.version.security_patch]:[2026-11-01]
- [ro.build.version.security_patch]:[2026-11-05]
For some devices on Android 10 or later, the Google Play system update will have a date string that matches the 2026-11-01 security patch level. Please see this article for more details on how to install security updates.
2. Why does this bulletin have two security patch levels?
This bulletin has two security patch levels so that Android partners have the flexibility to fix a subset of vulnerabilities that are similar across all Android devices more quickly. Android partners are encouraged to fix all issues in this bulletin and use the latest security patch level.
- Devices that use the 2026-11-01 security patch level must include all issues associated with that security patch level, as well as fixes for all issues reported in previous security bulletins.
- Devices that use the security patch level of 2026-11-05 or newer must include all applicable patches in this (and previous) security bulletins.
Partners are encouraged to bundle the fixes for all issues they are addressing in a single update.
3. What do the entries in the Type column mean?
Entries in the Type column of the vulnerability details table reference the classification of the security vulnerability.
| Abbreviation | Definition |
|---|---|
| RCE | Remote code execution |
| EoP | Elevation of privilege |
| ID | Information disclosure |
| DoS | Denial of service |
| N/A | Classification not available |
4. What do the entries in the References column mean?
Entries under the References column of the vulnerability details table may contain a prefix identifying the organization to which the reference value belongs.
| Prefix | Reference |
|---|---|
| A- | Android bug ID |
| QC- | Qualcomm reference number |
| M- | MediaTek reference number |
| N- | NVIDIA reference number |
| B- | Broadcom reference number |
| U- | UNISOC reference number |
5. What does an * next to the Android bug ID in the References column mean?
Issues that are not publicly available have an * next to the corresponding reference ID. The update for that issue is generally contained in the latest binary drivers for Pixel devices available from the Google Developer site.
6. Why are security vulnerabilities split between this bulletin and device / partner security bulletins, such as the Pixel bulletin?
Security vulnerabilities that are documented in this security bulletin are required to declare the latest security patch level on Android devices. Additional security vulnerabilities that are documented in the device / partner security bulletins are not required for declaring a security patch level. Android device and chipset manufacturers may also publish security vulnerability details specific to their products, such as Google, Huawei, LGE, Motorola, Nokia, or Samsung.
Versions
| Version | Date | Notes |
|---|---|---|
| 1.0 | November 2, 2026 | Bulletin Published |