CyberSecBulletin

Google vulnerabilities

We track 4,264 vulnerabilities in Google products across 60+ products. 4,254 are rated high or critical, and 93 have been exploited in real attacks. The most recent was published on November 11, 2026.

4,264vulnerabilities
623critical
3,631high
93exploited
8.5average CVSS score

Latest Google vulnerabilities

  • 8.8 High severity

    Chrome: Access of Resource Using Incompatible Type

    CVE-2025-2135GoogleEPSS 6.57%

    Type Confusion in V8 in Google Chrome prior to 134.0.6998.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Access of Resource Using Incompatible Type

    CVE-2025-1920Google

    Type Confusion in V8 in Google Chrome prior to 134.0.6998.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

  • 7.8 High severity

    Android: Improper Preservation of Permissions

    CVE-2024-56192Google

    In wl_notify_gscan_event of wl_cfgscan.c, there is a possible out of bounds write 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.

  • 8.4 High severity

    Android: Improper Preservation of Permissions

    CVE-2024-56191Google

    In dhd_process_full_gscan_result of dhd_pno.c, there is a possible EoP due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.8 High severity

    Chrome: Out-of-bounds Read

    CVE-2025-1919Google

    Out of bounds read in Media in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)

  • 8.8 High severity

    Chrome: Out-of-bounds Read

    CVE-2025-1918Google

    Out of bounds read in PDFium in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted PDF file. (Chromium security severity: Medium)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2025-1916Google

    Use after free in Profiles in Google Chrome prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

  • 8.1 High severity

    Chrome: Improper Limitation of a Pathname to a Restricted Directory

    CVE-2025-1915Google

    Improper Limitation of a Pathname to a Restricted Directory in DevTools in Google Chrome on Windows prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to bypass file access restrictions via a crafted Chrome Extensi

  • 8.8 High severity

    Chrome: Out-of-bounds Read

    CVE-2025-1914Google

    Out of bounds read in V8 in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

  • 7.8 High severity

    MT6765, MT6768, MT6833, MT6835, MT6853…: Out-of-bounds Write

    CVE-2025-20645MediaTek

    In KeyInstall, 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: AL

  • 8.8 High severity

    Chrome: Heap-based Buffer Overflow

    CVE-2025-1426Google

    Heap buffer overflow in GPU in Google Chrome on Android prior to 133.0.6943.126 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2025-1006Google

    Use after free in Network in Google Chrome prior to 133.0.6943.126 allowed a remote attacker to potentially exploit heap corruption via a crafted web app. (Chromium security severity: Medium)

  • 8.8 High severity

    Chrome: Heap-based Buffer Overflow

    CVE-2025-0999Google

    Heap buffer overflow in V8 in Google Chrome prior to 133.0.6943.126 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

  • 8.1 High severity

    Chrome: Use After Free

    CVE-2025-0997Google

    Use after free in Navigation in Google Chrome prior to 133.0.6943.98 allowed a remote attacker to potentially exploit heap corruption via a crafted Chrome Extension. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2025-0995Google

    Use after free in V8 in Google Chrome prior to 133.0.6943.98 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Chrome: Use After Free

    CVE-2025-0762Google

    Use after free in DevTools in Google Chrome prior to 132.0.6834.159 allowed a remote attacker to potentially exploit heap corruption via a crafted Chrome Extension. (Chromium security severity: Medium)

  • 8.4 High severity

    Android: Missing Authorization

    CVE-2024-40677Google

    In shouldSkipForInitialSUW of AdvancedPowerUsageDetail.java, there is a possible way to bypass factory reset protections due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User in

  • 7.7 High severity

    Android: Access of Resource Using Incompatible Type

    CVE-2024-40676Google

    In checkKeyIntent of AccountManagerService.java, there is a possible way to bypass intent security check and install an unknown app due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User

  • 7.5 High severity

    Android: Loop with Unreachable Exit Condition

    CVE-2024-40675Google

    In parseUriInternal of Intent.java, there is a possible infinite loop due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Improper Preservation of Permissions

    CVE-2024-40672Google

    In onCreate of ChooserActivity.java, there is a possible way to bypass factory reset protections due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed

  • 8.4 High severity

    Android: Use After Free

    CVE-2024-40670Google

    In TBD of TBD, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2024-40669Google

    In TBD of TBD, there is a possible use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2024-40651Google

    In TBD of TBD, there is a possible use-after-free due to a logic error in the code. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2024-40649Google

    In TBD of TBD, there is a possible use-after-free due to a logic error in the code. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 8.4 High severity

    Android: Use After Free

    CVE-2024-34748Google

    In _DevmemXReservationPageAddress of devicemem_server.c, there is a possible use-after-free due to improper casting. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed f

  • 8.4 High severity

    Android: Integer Overflow or Wraparound

    CVE-2024-34733Google

    In DevmemXIntMapPages of devicemem_server.c, there is a possible arbitrary code execution due to an integer overflow. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed

  • 8.4 High severity

    Android: Concurrent Execution using Shared Resource with Improper Synchronization

    CVE-2024-34732Google

    In RGXMMUCacheInvalidate of rgxmem.c, there is a possible arbitrary code execution due to a race condition. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploi

  • 7.5 High severity

    Chrome: Out-of-bounds Read

    CVE-2025-0612Google

    Out of bounds memory access in V8 in Google Chrome prior to 132.0.6834.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

  • 8.2 High severity

    Chrome: Heap-based Buffer Overflow

    CVE-2025-0611Google

    Object corruption in V8 in Google Chrome prior to 132.0.6834.110 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

  • 8.8 High severity

    Android: Out-of-bounds Write

    CVE-2024-49749Google

    In DGifSlurp of dgif_lib.c, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 9.8 Critical severity

    Android: Out-of-bounds Write

    CVE-2024-49748Google

    In gatts_process_primary_service_req of gatt_sr.cc, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 9.8 Critical severity

    Android: Improper Control of Generation of Code

    CVE-2024-49747Google

    In gatts_process_read_by_type_req of gatt_sr.cc, there is a possible out of bounds write due to a logic error in the code. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 7.8 High severity

    Android: Out-of-bounds Write

    CVE-2024-49745Google

    In growData of Parcel.cpp, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 7.8 High severity

    Android: Incorrect Default Permissions

    CVE-2024-49744Google

    In checkKeyIntentParceledCorrectly of AccountManagerService.java, there is a possible way to bypass parcel mismatch mitigation due to unsafe deserialization. This could lead to local escalation of privilege with no additional execution privileges needed. User

  • 7.8 High severity

    Android: Improper Privilege Management

    CVE-2024-49742Google

    In onCreate of NotificationAccessConfirmationActivity.java , there is a possible way to hide an app with notification access in Settings due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges

  • 7.8 High severity

    Android: Out-of-bounds Write

    CVE-2024-49738Google

    In writeInplace of Parcel.cpp, there is a possible out of bounds write. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 7.8 High severity

    Android: Incorrect Default Permissions

    CVE-2024-49737Google

    In applyTaskFragmentOperation of WindowOrganizerController.java, there is a possible way to launch arbitrary activities as the system UID due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges

  • 7.8 High severity

    Android: Incorrect Default Permissions

    CVE-2024-49735Google

    In multiple locations, there is a possible failure to persist permissions settings due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • 7.5 High severity

    Android: Exposure of Sensitive Information to an Unauthorized Actor

    CVE-2024-49734Google

    In multiple functions of ConnectivityService.java, there is a possible way for a Wi-Fi AP to determine what site a device has connected to through a VPN due to side channel information disclosure. This could lead to remote information disclosure with no additi

  • 7.8 High severity

    Android: Incorrect Default Permissions

    CVE-2024-49732Google

    In multiple functions of CompanionDeviceManagerService.java, there is a possible way to grant permissions without user consent due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. U