16,977 known vulnerabilities
Top Products
Use after free in Serial in Google Chrome prior to 130.0.6723.116 allowed a remote attacker to potentially exploit heap
Use after free in Family Experiences in Google Chrome on Android prior to 130.0.6723.116 allowed a remote attacker to po
There exists a Path Traversal vulnerability in Safearchive on Platforms with Case-Insensitive Filesystems (e.g., NTFS).
In vdec, there is a possible out of bounds read due to improper structure design. This could lead to local information d
In vdec, there is a possible out of bounds read due to improper structure design. This could lead to local information d
In vdec, there is a possible out of bounds read due to improper structure design. This could lead to local information d
In KeyInstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In KeyInstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In mms, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In mms, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In vdec, there is a possible out of bounds read due to improper structure design. This could lead to local information d
In ccu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ccu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ccu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In isp, there is a possible out of bounds read due to a missing bounds check. This could lead to local denial of service
In ccu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ccu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ccu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In atci, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
In da, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclo
In m4u, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In da, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pri
Use after free in WebRTC in Google Chrome prior to 130.0.6723.92 allowed a remote attacker to potentially exploit heap c
Out of bounds write in Dawn in Google Chrome prior to 130.0.6723.92 allowed a remote attacker to perform out of bounds m
In valid_address of syscall.c, there is a possible out of bounds read due to an incorrect bounds check. This could lead
In vring_init of external/headers/include/virtio/virtio_ring.h, there is a possible out of bounds write due to a logic e
there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure wi
In lwis_allocator_free of lwis_allocator.c, there is a possible memory corruption due to a use after free. This could le
Android before 2024-10-05 on Google Pixel devices allows privilege escalation in the ABL component, A-329163861.
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ACPM component, A-315191818.
In TrustySharedMemoryManager::GetSharedMemory of ondevice/trusty/trusty_shared_memory_manager.cc, there is a possible ou
In ffu_flash_pack of ffu.c, there is a possible out of bounds read due to an integer overflow. This could lead to local
In sm_mem_compat_get_vmm_obj of lib/sm/shared_mem.c, there is a possible arbitrary physical memory access due to imprope
In gsc_gsa_rescue of gsc_gsa.c, there is a possible out of bounds read due to an incorrect bounds check. This could lead
In ppmp_protect_buf of drm_fw.c, there is a possible information disclosure due to a logic error in the code. This could
In vring_size of external/headers/include/virtio/virtio_ring.h, there is a possible out of bounds write due to an intege
there is a possible man-in-the-middle attack due to a logic error in the code. This could lead to remote escalation of p
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ACPM component, A-331255656.
In sms_ExtractCbLanguage of sms_CellBroadcast.c, there is a possible out of bounds read due to a missing bounds check. T
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the ABL component, A-331966488.
In ProtocolEmbmsSaiListAdapter::Init() of protocolembmsadapter.cpp, there is a possible out of bounds read due to a miss
In pmucal_rae_handle_seq_int of flexpmu_cal_rae.c, there is a possible out of bounds read due to a buffer overflow. This
In ufshc_scsi_cmd of ufs.c, there is a possible stack variable use after free due to a use after free. This could lead t
there is a possible privilege escalation due to an insecure default value. This could lead to local escalation of privil
In ProtocolMiscHwConfigChangeAdapter::GetData() of protocolmiscadapter.cpp, there is a possible out-of-bounds read due t
Android before 2024-10-05 on Google Pixel devices allows privilege escalation in the ABL component, A-330537292.
In pmucal_rae_handle_seq_int of flexpmu_cal_rae.c, there is a possible arbitrary write due to uninitialized data. This c
In mm_GetMobileIdIndexForNsUpdate of mm_GmmPduCodec.c, there is a possible out of bounds write due to an incorrect bound
there is a possible Null Pointer Dereference (modem crash) due to improper input validation. This could lead to remote d
Android before 2024-10-05 on Google Pixel devices allows information disclosure in the modem component, A-299774545.
Frequently Asked Questions
How many CVEs affect Google?
Google has 16,977 CVE records in our database, including 1160 critical and 8152 high severity vulnerabilities. 94 of these are listed in CISA's Known Exploited Vulnerabilities catalog.
What are the most severe Google vulnerabilities?
Google has 1160 critical severity (CVSS 9.0+) and 8152 high severity (CVSS 7.0-8.9) vulnerabilities. 94 vulnerabilities are confirmed as actively exploited in the wild.
How can I scan for Google vulnerabilities?
CyberStrike's AI-powered security agents automatically detect vulnerabilities in Google products across your infrastructure. The platform provides continuous pentesting, DAST scanning, and real-time vulnerability monitoring with actionable remediation guidance.
Detect Google Vulnerabilities
CyberStrike scans your infrastructure for Google vulnerabilities and provides real-time remediation guidance.
Get Started