16,977 known vulnerabilities
Top Products
In RGXDestroyHWRTData of rgxta3d.c, there is a possible arbitrary code execution due to an uncaught exception. This cou
In visitUris of Notification.java, there is a possible way to display images from another user due to a confused deputy.
In RGXDestroyZSBufferKM of rgxta3d.c, there is a possible arbitrary code execution due to an uncaught exception. This co
In MMU_UnmapPages of mmu_common.c, there is a possible out of bounds read due to improper input validation. This could l
In DevmemIntChangeSparse of devicemem_server.c, there is a possible out of bounds write due to an integer overflow. This
In OSMMapPMRGeneric of pmr_os.c, there is a possible out of bounds write due to an uncaught exception. This could lea
In PMRChangeSparseMemOSMem of physmem_osmem_linux.c, there is a possible out of bounds write due to an incorrect bounds
In HTBLogKM of htbserver.c, there is a possible information disclosure due to log information disclosure. This could lea
In PMRChangeSparseMemOSMem of physmem_osmem_linux.c, there is a possible out of bounds write due to an incorrect bounds
In PMRWritePMPageList of TBD, there is a possible out of bounds write due to an integer overflow. This could lead to loc
In PMRChangeSparseMemOSMem of physmem_osmem_linux.c, there is a possible arbitrary code execution due to a use after fre
In DevmemIntAcquireRemoteCtx of devicemem_server.c, there is a possible arbitrary code execution due to a race condition
In RGXBackingZSBuffer of rgxta3d.c, there is a possible arbitrary code execution due to a use after free. This could lea
In DevmemIntMapPMR of devicemem_server.c, there is a possible arbitrary code execution due to a use after free. This cou
In PMR_ReadBytes of pmr.c, there is a possible arbitrary code execution due to a use after free. This could lead to loca
In RGXUnbackingZSBuffer of rgxta3d.c, there is a possible arbitrary code execution due to a use after free. This could l
A potential logging of the firestore key via logging within nodejs-firestore exists - Developers who were logging object
In display drm, there is a possible out of bounds read due to a missing bounds check. This could lead to local escalatio
In display drm, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In display drm, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In display drm, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In mmp, there is a possible memory corruption due to an incorrect bounds check. This could lead to local escalation of p
In display drm, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escal
In display drm, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escal
In display drm, there is a possible out of bounds read due to a missing bounds check. This could lead to local escalatio
In display, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local escalation
In display, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local escalation
In display, there is a possible classic buffer overflow due to a missing bounds check. This could lead to local escalati
In meta, there is a possible classic buffer overflow due to a missing bounds check. This could lead to local escalation
In GZ, there is a possible information disclosure due to a missing data erasing. This could lead to local information di
In display, there is a possible out of bounds read due to an incorrect status check. This could lead to local informatio
In display, there is a possible out of bounds read due to an incorrect status check. This could lead to local informatio
In aee, there is a possible escalation of privilege due to a missing permission check. This could lead to local escalati
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In rpmb, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
In cameraisp, there is a possible information disclosure due to improper input validation. This could lead to local info
In decoder, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In decoder, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of p
In cmdq, there is a possible out of bounds write due to type confusion. This could lead to local escalation of privilege
In vdec, there is a possible out of bounds write due to type confusion. This could lead to local escalation of privilege
In audio, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In gnss service, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In enginnermode service, there is a possible way to write permission usage records of an app due to a missing permission
In telecom service, there is a possible missing permission check. This could lead to local escalation of privilege with
In camera service, there is a possible missing permission check. This could lead to local escalation of privilege with n
In power manager, there is a possible missing permission check. This could lead to local escalation of privilege with no
In telecom service, there is a possible missing permission check. This could lead to local escalation of privilege with
In telecom service, there is a possible missing permission check. This could lead to local denial of service with no add
In telecom service, there is a possible missing permission check. This could lead to local escalation of privilege with
In sysui, there is a possible missing permission check. This could lead to local denial of service with no additional ex
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