16,977 known vulnerabilities
Top Products
Use after free in ANGLE in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially exploit heap co
Incorrect security UI in Split View in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform UI spoo
Incorrect security UI in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to spoof the content
Insufficient policy enforcement in Network in Google Chrome prior to 144.0.7559.59 allowed an attack who obtained a netw
Incorrect security UI in Digital Credentials in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perfor
Inappropriate implementation in Downloads in Google Chrome on Windows prior to 144.0.7559.59 allowed a remote attacker t
Inappropriate implementation in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform an out o
Inappropriate implementation in Blink in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to pe
Inappropriate implementation in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially expl
Out of bounds memory access in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially explo
In cpm_fwtp_msg_handler of cpm/google/lib/tracepoint/cpm_fwtp_ipc.c, there is a possible memory overwrite due to imprope
In key-based pairing, there is a possible ID due to a logic error in the code. This could lead to remote (proximal/adjac
Insufficient policy enforcement in WebView tag in Google Chrome prior to 143.0.7499.192 allowed an attacker who convince
In dpe, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privi
In dpe, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if
In dpe, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if
In dpe, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege if
In dpe, there is a possible memory corruption due to an integer overflow. This could lead to local escalation of privile
In geniezone, there is a possible memory corruption due to use after free. This could lead to local escalation of privil
In seninf, there is a possible memory corruption due to a race condition. This could lead to local escalation of privile
In mminfra, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In c2ps, there is a possible memory corruption due to use after free. This could lead to local escalation of privilege i
In battery, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In battery, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In imgsys, there is a possible out of bounds write due to improper input validation. This could lead to local escalation
In KeyInstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In display, there is a possible memory corruption due to use after free. This could lead to local escalation of privileg
In display, there is a possible memory corruption due to use after free. This could lead to local escalation of privileg
In display, there is a possible memory corruption due to use after free. This could lead to local escalation of privileg
In display, there is a possible memory corruption due to uninitialized data. This could lead to local escalation of priv
In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In display, there is a possible memory corruption due to use after free. This could lead to local escalation of privileg
In display, there is a possible memory corruption due to use after free. This could lead to local escalation of privileg
In display, there is a possible use after free due to a race condition. This could lead to local escalation of privilege
In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
Out of bounds read and write in V8 in Google Chrome prior to 143.0.7499.147 allowed a remote attacker to potentially exp
Use after free in WebGPU in Google Chrome prior to 143.0.7499.147 allowed a remote attacker to potentially exploit heap
The Cordova plugin cordova-plugin-x-socialsharing (SocialSharing-PhoneGap-Plugin) for Android 6.0.4, registers an export
Inappropriate implementation in Toolbar in Google Chrome on Android prior to 143.0.7499.110 allowed a remote attacker to
Use after free in Password Manager in Google Chrome prior to 143.0.7499.110 allowed a remote attacker to potentially per
Out of bounds memory access in ANGLE in Google Chrome on Mac prior to 143.0.7499.110 allowed a remote attacker to perfor
In U-Boot of append_uint32_le(), there is a possible fault injection due to a logic error in the code. This could lead t
In AudioDecoder::HandleProduceRequest of audio_decoder.cc, there is a possible out of bounds write due to an incorrect b
In GetTachyonCommand of tachyon_server_common.h, there is a possible out of bounds write due to an integer overflow. Thi
In trusty_ffa_mem_reclaim of shared-mem-smcall.c, there is a possible memory corruption due to uninitialized data. This
In bigo_worker_thread of private/google-modules/video/gchips/bigo.c, there is a possible use after free due to a race co
In tracepoint_msg_handler of cpm/google/lib/tracepoint/tracepoint_ipc.c, there is a possible memory overwrite due to imp
In GetHostAddress of gxp_buffer.h, there is a possible out of bounds write due to a missing bounds check. This could lea
In GetHostAddress of gxp_buffer.h, there is a possible out of bounds write due to a missing bounds check. This could lea
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