16,977 known vulnerabilities
Top Products
Insufficient policy enforcement in Downloads in Google Chrome prior to 88.0.4324.96 allowed an attacker who convinced a
Inappropriate implementation in DevTools in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially
Insufficient policy enforcement in File System API in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to b
Insufficient policy enforcement in File System API in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to b
Insufficient policy enforcement in File System API in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to b
Heap buffer overflow in Blink in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially exploit he
Insufficient policy enforcement in extensions in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to bypass
Insufficient policy enforcement in extensions in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to bypass
Insufficient policy enforcement in File System API in Google Chrome on Windows prior to 88.0.4324.96 allowed a remote at
Potential user after free in Speech Recognizer in Google Chrome on Android prior to 88.0.4324.96 allowed a remote attack
Insufficient data validation in File System API in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to bypa
Use after free in Blink in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially exploit heap cor
Use after free in Omnibox in Google Chrome on Linux prior to 88.0.4324.96 allowed a remote attacker to potentially perfo
Use after free in WebSQL in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially exploit heap co
Use after free in Media in Google Chrome prior to 88.0.4324.96 allowed a remote attacker who had compromised the rendere
Insufficient data validation in V8 in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially perfo
Insufficient policy enforcement in Cryptohome in Google Chrome prior to 88.0.4324.96 allowed a local attacker to perform
Use after free in WebRTC in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially exploit heap co
OPPO Android Phone with MTK chipset and Android 8.1/9/10/11 versions have an information leak vulnerability. The “adb sh
In wlan driver, there is a possible system crash due to a missing bounds check. This could lead to remote denial of serv
In ged, there is a possible system crash due to an improper input validation. This could lead to local denial of service
In display driver, there is a possible memory corruption due to a use after free. This could lead to local escalation of
In vpu, 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 read due to a missing bounds check. This could lead to local information discl
In vpu, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In mobile_log_d, there is a possible escalation of privilege due to improper input validation. This could lead to local
In mtkpower, there is a possible memory corruption due to a missing bounds check. This could lead to local escalation of
In kisd, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
An issue was discovered on LG mobile devices with Android OS 8.0, 8.1, 9.0, and 10 software. The USB laf gadget has a us
An issue was discovered on LG Wing mobile devices with Android OS 10 software. The biometric sensor has weak security pr
An issue was discovered on LG mobile devices with Android OS 8.0, 8.1, 9.0, and 10 software. In preloaded applications,
In display driver, there is a possible memory corruption due to a use after free. This could lead to local escalation of
In mobile_log_d, there is a possible command injection due to improper input validation. This could lead to local escala
In mobile_log_d, there is a possible command injection due to a missing bounds check. This could lead to local escalatio
In aee, there is a possible memory corruption due to a stack buffer overflow. This could lead to local escalation of pri
In kisd, there is a possible out of bounds read due to improper input validation. This could lead to local escalation of
In netdiag, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalatio
In netdiag, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In netdiag, there is a possible command injection due to improper input validation. This could lead to local escalation
In netdiag, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In netdiag, there is a possible command injection due to improper input validation. This could lead to local escalation
In kisd, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of priv
In ged, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privi
In kisd, there is a possible memory corruption due to a heap buffer overflow. This could lead to local escalation of pri
In RT regmap driver, there is a possible memory corruption due to type confusion. This could lead to local denial of ser
In checkGrantUriPermission of UriGrantsManagerService.java, there is a possible way to access contacts due to a permissi
In checkGrantUriPermission of UriGrantsManagerService.java, there is a possible permissions bypass. This could lead to l
In A2DP_GetCodecType of a2dp_codec_config, there is a possible out-of-bounds read due to improper input validation. This
Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to
NVIDIA SHIELD TV, all versions prior to 8.2.2, contains a vulnerability in the NVHost function, which may lead to abnorm
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