Fixing the latest bugs and exploits in Android every month.

Google has detailed the latest Android Security Bulletin and released the fixes for Nexus and Pixel devices.

These are exploits and other security concerns that affect Android as a whole. Issues with the operating system, kernel patches, and driver updates may not affect any particular device, but these need to be fixed in the Android base by the folks maintaining the operating system code. That means Google, and they've detailed the things they have improved for this month.

Updated factory images for Pixel and Nexus devices that are supported are available, and over-the-air updates are rolling out to users. If you don't want to wait, you can download and flash the factory image or OTA update file manually, and here are some handy instructions to get you started.

How to manually update your Nexus or Pixel

The company that made your phone uses these patches to send an update out to you.

These changes have been released to the people making Android phones for at least 30 days, but Google can't force anyone to deliver them to you. If you're using a phone from Samsung, LG, or anyone besides Google, you'll need to wait for them to send an update and shouldn't try to flash any of the above files.

Of course, Google has safety checks in place to prevent any problems on your phone because of any security exploits. Verify Apps and SafetyNet are at work anytime you add an app to your phone, and seamless updates to Google Play Services will keep them up to date regardless of any hold up from a manufacturer or carrier. Details and incident numbers can be found in the yearly Android Security Review (.pdf file).

Highlights for November 2017

November 2017's update comes with three patch dates: 11/01/2017, 11/05/2017 and 11/06/2017.

  • This month's patch updates the network stack to patch the KRACK Wi-Fi exploit.
  • The Android framework has once again been patched to prevent an exploit that bypass user interaction requirements in order to gain access to additional permissions.
  • The media framework and the Android system itself were again patched to combat the ever-present attacks through media containers. This has been a monthly thing for over a year and will certainly continue.
  • Critical updates were applied as far back as Android 5.02 for OEMs to use to patch their existing devices if they wish.
  • Broadcom, MediaTek, NVIDIA, and Qualcomm have each patched a number of drivers that could potentially allow remote attackers to execute code.

If you get an update with a patch date of 10/05/2017, you also have every issue addressed by the 10/01/2017 update in place. Devices that receive a patch with the 11/06/2017 date have all the November fixes in place as well as all previous patches. This is something new and we're hopeful that it continues.

Previous bulletin highlights

Here are summaries and highlights of recent patches from the monthly Android Security Bulletin. As with the current bulletin, these issues were also mitigated by Google's Verify Apps, Safety Net, and seamless updates to Google Play Services.

Highlights for October 2017

October 2017's update comes with two patch dates: 10/01/2017 and 10/05/2017.

  • This month's patch updates several critical components to prevent privileged code execution, both locally and remote.
  • The Android framework has been patched to prevent an exploit that bypass user interaction requirements in order to gain access to additional permissions.
  • The media framework and the Android system itself were patched to prevent execute arbitrary code within the context of a privileged process.
  • Critical updates were applied as far back as Android 4.4
  • Broadcom, MediaTek, and Qualcomm have each patched a number of drivers that could potentially allow remote attackers to execute code.

If you get an update with a patch date of 10/05/2017, you also have every issue addressed by the 10/01/2017 update in place.

Highlights for September 2017

September 2017's update comes with two patch dates: 09/01/2017 and 09/05/2017.

  • The main issue this month revolves, once again, around a vulnerability in the media framework that, when paired with exploitative code, could remotely execute malware on a user's device.
  • Some of these patches go back to Android 4.4 KitKat.
  • A runtime bug has been patched that would allow a remote user to execute code that could cause an app to hang.
  • Broadcom has once again issued a number of patches for its Wi-Fi drivers.
  • MediaTek and Qualcomm have each patched a number of drivers that could potentially allow remote attackers to execute code.

If you get an update with a patch date of 09/05/2017, you also have every issue addressed by the 09/01/2017 update in place.

Highlights for August 2017

August 2017's update comes with two patch dates: 08/01/2017 and 08/05/2017.

  • A moderate issue in the Android runtime that could enable privileged code execution has been patched.
  • Again we see numerous issues that could allow remote code execution through the media libraries patched, with some changes going back to Android 4.4.
  • Qualcomm has patched numerous escalation of privilege issues in the Snapdragon platform. These include moderate vulnerability patches for video, the GPU, and USB input/output. Since these include closed source changes, new versions are available from Qualcomm for your device manufacturer to implement as needed.
  • MediaTek and Broadcom have also supplied patched device drivers for a range of issues rated from low to moderate. Any of these binaries that are applicable to Nexus or Pixel devices are available at the Google Developer site.

If you get an update with a patch date of 08/05/2017, you also have every issue addressed by the 08/01/2017 update in place.

July 2017

July 2017's update comes with two patch dates: 07/01/2017 and 07/05/2017.

  • An issue in the Android runtime that could enable remote code execution has been patched.
  • Over 20 issues that could allow remote code execution through the media libraries have been patched, with some changes going back to Android 4.4.
  • Qualcomm has patched numerous escalation of privilege issues in the Snapdragon platform. These include both closed source and open source changes. The closed source changes are available from Qualcomm for your device manufacturer to implement as needed.
  • NVIDIA, MediaTek, HTC, and Broadcom have also supplied patched device drivers for a range of issues rated from low to moderate. Any of these binaries that are applicable to Nexus or Pixel devices are available at the Google Developer site.

If you get an update with a patch date of 07/05/2017, you also have every issue addressed by the 07/01/2017 update in place.

June 2017

June 2017's update comes with two patch dates: 06/01/2017 and 06/05/2017.

  • Google Pixel devices for the Canadian carrier Rogers will get a hotfix for VoLTE issues in addition to security updates.
  • Qualcomm has patched a slew of device drivers for the Snapdragon platform. Most were of moderate severity but a Bluetooth-specific update is a critical patch.
  • NVIDIA, MediaTek, and Synaptics have also supplied patched device drivers for a range of issues rated from low to moderate. Any of these binaries that are applicable to Nexus or Pixel devices are available at the Google Developer site.
  • Exploits that allow remote code execution while viewing media in an email, SMS or the browser continue to be addressed as new ones arise. This is a never-ending fight and a reason why monthly patches are important.

If you get an update with a patch date of 06/05/2017, you also have every issue addressed by the 06/01/2017 update in place.

May 2017

May 2017's update comes with two patch dates: 05/01/2017 and 05/05/2017.

  • Qualcomm has patched an exploit that potentially could allow unauthorized bootloader access for devices using Snapdragon 800 series processors. Motorola has issued a separate update to address the Nexus 6.
  • A specific vulnerability in GIFLIB that can cause memory corruption when a bad file is received has been isolated and patched. This patch applies to Android 4.4 or higher and has been merged into AOSP.
  • Qualcomm, NVIDIA and MediaTek continue to address exploits that affect their "drivers" and have again refined the code for May 2017. Any of these binaries that are applicable to Nexus or Pixel devices are available at the Google Developer site.
  • Several moderate exploits in the Bluetooth stack that could allow a user to receive a file without explicit permission have been addressed. Patches have been merged into AOSP back to Android 4.4.

If you get an update with a patch date of 05/05/2017, you also have every issue addressed by the 05/01/2017 update in place.


Archives of all previous Android Security Bulletins are available at the Android Security website.

See the Android Security website for details on all bulletins

Updated November 2017: Added information for the latest patch from Google.