Google CVEs
9,109 CVEs and advisories name Google as an affected vendor, 82 of them on CISA's Known Exploited Vulnerabilities catalog, newest first. Follow it as a feed.
- CVE-2024-0517Out of bounds write in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a cr
- CVE-2024-0333Insufficient data validation in Extensions in Google Chrome prior to 120.0.6099.216 allowed an attacker in a privileged network position to
- CVE-2024-0225Use after free in WebGPU in Google Chrome prior to 120.0.6099.199 allowed a remote attacker to potentially exploit heap corruption via a cra
- CVE-2024-0224Use after free in WebAudio in Google Chrome prior to 120.0.6099.199 allowed a remote attacker to potentially exploit heap corruption via a c
- CVE-2024-0223Heap buffer overflow in ANGLE in Google Chrome prior to 120.0.6099.199 allowed a remote attacker to potentially exploit heap corruption via
- CVE-2024-0222Use after free in ANGLE in Google Chrome prior to 120.0.6099.199 allowed a remote attacker who had compromised the renderer process to poten
- CVE-2023-48418User Build misconfiguration resulting in local escalation of privilege
- CVE-2023-6339Google Nest WiFi Pro root code-execution & user-data compromise
- CVE-2023-4164There is a possible information disclosure due to a missing permission check in Pixel Watch
- CVE-2023-48419An attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in EoP
- CVE-2023-7024Heap buffer overflow in WebRTC in Google Chrome prior to 120.0.6099.129 allowed a remote attacker to potentially exploit heap corruption via
- CVE-2023-3742Insufficient policy enforcement in ADB in Google Chrome on ChromeOS prior to 114.0.5735.90 allowed a local attacker to bypass device policy
- CVE-2023-6707Use after free in CSS in Google Chrome prior to 120.0.6099.109 allowed a remote attacker to potentially exploit heap corruption via a crafte
- CVE-2023-6706Use after free in FedCM in Google Chrome prior to 120.0.6099.109 allowed a remote attacker who convinced a user to engage in specific UI int
- CVE-2023-6705Use after free in WebRTC in Google Chrome prior to 120.0.6099.109 allowed a remote attacker to potentially exploit heap corruption via a cra
- CVE-2023-6704Use after free in libavif in Google Chrome prior to 120.0.6099.109 allowed a remote attacker to potentially exploit heap corruption via a cr
- CVE-2023-6703Use after free in Blink in Google Chrome prior to 120.0.6099.109 allowed a remote attacker to potentially exploit heap corruption via a craf
- CVE-2023-6702Type confusion in V8 in Google Chrome prior to 120.0.6099.109 allowed a remote attacker to potentially exploit heap corruption via a crafted
- CVE-2023-6181An oversight in BCB handling of reboot reason that allows for persistent code execution
- CVE-2023-48425U-Boot vulnerability resulting in persistent Code Execution
- CVE-2023-48424U-Boot shell vulnerability resulting in Privilege escalation in a production device
- CVE-2023-48417Missing Permission checks resulting in unauthorized access and Manipulation in KeyChainActivity Application
- CVE-2023-48423In dhcp4_SetPDNAddress of dhcp4_Main.c, there is a possible out of bounds write due to a missing bounds check.
- CVE-2023-48422In Init of protocolnetadapter.cpp, there is a possible out of bounds read due to a missing bounds check.
- CVE-2023-48421In gpu_pixel_handle_buffer_liveness_update_ioctl of private/google-modules/gpu/mali_kbase/platform/pixel/pixel_gpu_slc.c, there is a possibl
- CVE-2023-48420there is a possible use after free due to a race condition.
- CVE-2023-48416In multiple locations, there is a possible null dereference due to a missing null check.
- CVE-2023-48415In Init of protocolembmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check.
- CVE-2023-48414In the Pixel Camera Driver, there is a possible use after free due to a logic error in the code.
- CVE-2023-48413In Init of protocolnetadapter.cpp, there is a possible out of bounds read due to a missing bounds check.