16,977 known vulnerabilities
Top Products
There is a possible Local bypass of user interaction due to an insecure default value. This could lead to local informat
In lwis_device_event_states_clear_locked of lwis_event.c, there is a possible privilege escalation due to a double free.
Type Confusion in V8 in Google Chrome prior to 130.0.6723.69 allowed a remote attacker to potentially exploit heap corru
Type Confusion in V8 in Google Chrome prior to 130.0.6723.69 allowed a remote attacker to potentially exploit heap corru
Inappropriate implementation in Extensions in Google Chrome prior to 130.0.6723.69 allowed a remote attacker to bypass s
There exists an insecure default user permission in Google Cloud Migrate to containers from version 1.1.0 to 1.2.2 Windo
Inappropriate implementation in Navigations in Google Chrome prior to 130.0.6723.58 allowed a remote attacker to bypass
Insufficient data validation in DevTools in Google Chrome on Windows prior to 130.0.6723.58 allowed a remote attacker wh
Inappropriate implementation in Payments in Google Chrome prior to 130.0.6723.58 allowed a remote attacker who convinced
Insufficient data validation in Downloads in Google Chrome prior to 130.0.6723.58 allowed a remote attacker who convince
Inappropriate implementation in Permissions in Google Chrome prior to 130.0.6723.58 allowed a remote attacker who convin
Use after free in ParcelTracking in Google Chrome on iOS prior to 130.0.6723.58 allowed a remote attacker who convinced
Use after free in Dawn in Google Chrome prior to 130.0.6723.58 allowed a remote attacker to potentially exploit heap cor
Use after free in DevTools in Google Chrome prior to 130.0.6723.58 allowed a remote attacker who had compromised the ren
Inappropriate implementation in PictureInPicture in Google Chrome prior to 130.0.6723.58 allowed a remote attacker to pe
Use after free in UI in Google Chrome on iOS prior to 130.0.6723.58 allowed a remote attacker who convinced a user to en
Inappropriate implementation in WebAuthentication in Google Chrome on Android prior to 130.0.6723.58 allowed a local att
Use after free in WebAuthentication in Google Chrome prior to 130.0.6723.58 allowed a remote attacker to potentially exp
Use after free in AI in Google Chrome prior to 130.0.6723.58 allowed a remote attacker to potentially exploit heap corru
An HTTP Request Smuggling vulnerability in Looker allowed an unauthorized attacker to capture HTTP responses destined fo
Type confusion in WebAssembly in Google Chrome prior to 126.0.6478.126 allowed a remote attacker to execute arbitrary co
In DRM service, there is a possible system crash due to null pointer dereference. This could lead to local denial of ser
In DRM service, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial o
In linkturbonative service, there is a possible command injection due to improper input validation. This could lead to l
In linkturbonative service, there is a possible command injection due to improper input validation. This could lead to l
In linkturbonative service, there is a possible command injection due to improper input validation. This could lead to l
Type Confusion in V8 in Google Chrome prior to 129.0.6668.100 allowed a remote attacker to potentially exploit heap corr
Type Confusion in V8 in Google Chrome prior to 129.0.6668.100 allowed a remote attacker to perform an out of bounds memo
Improper check for exception conditions in Knox Guard prior to SMR Oct-2024 Release 1 allows physical attackers to bypas
Integer overflow in libSEF.quram.so prior to SMR Oct-2024 Release 1 allows local attackers to write out-of-bounds memory
In wlan firmware, there is a possible out of bounds write due to improper input validation. This could lead to remote co
In wlan driver, there is a possible out of bounds read due to improper input validation. This could lead to remote infor
In wlan driver, there is a possible out of bounds write due to improper input validation. This could lead to remote code
In wlan driver, there is a possible out of bounds write due to improper input validation. This could lead to remote code
In power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In vdec, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disc
In m4u, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In m4u, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In vdec, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disc
In vdec, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
In vdec, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disc
In vdec, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
According to the researcher: "The TLS connections are encrypted against tampering or eavesdropping. However, the applica
In Logmanager service, there is a possible missing verification incorrect input. This could lead to local escalation of
In drm service, there is a possible out of bounds read due to a missing bounds check. This could lead to local denial of
In drm service, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial o
In UMTS RLC driver, there is a possible out of bounds read due to a missing bounds check. This could lead to remote deni
In UMTS RLC driver, there is a possible out of bounds write due to a missing bounds check. This could lead to remote den
Integer overflow in Skia in Google Chrome prior to 129.0.6668.70 allowed a remote attacker to perform an out of bounds m
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