16,977 known vulnerabilities
Top Products
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds read due to a missing bounds check. This could lead to information disclos
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In WiFi, the RSSI value and SSID information is broadcast as part of android.net.wifi.RSSI_CHANGE and android.net.wifi.S
In Platform, there is a possible bypass of user interaction requirements due to missing permission checks. This could le
Adobe Flash Player version 32.0.0.192 and earlier versions have a Same Origin Policy Bypass vulnerability. Successful ex
Adobe Flash Player 32.0.0.238 and earlier versions, 32.0.0.207 and earlier versions have a Use after free vulnerability.
Adobe Flash Player 32.0.0.238 and earlier versions, 32.0.0.207 and earlier versions have a Same Origin Method Execution
In the Android kernel in VPN routing there is a possible information disclosure. This could lead to remote information d
In the Android kernel in the video driver there is a use after free due to a race condition. This could lead to local es
In the Android kernel in Pixel C USB monitor driver there is a possible OOB write due to a missing bounds check. This co
In the Android kernel in the video driver there is a kernel pointer leak due to a WARN_ON statement. This could lead to
In the Android kernel in i2c driver there is a possible out of bounds write due to memory corruption. This could lead to
In the Android kernel in F2FS touch driver there is a possible out of bounds read due to improper input validation. This
In the Android kernel in SEC_TS touch driver there is a possible out of bounds read due to a missing bounds check. This
In the Android kernel in the touchscreen driver there is a possible out of bounds write due to a missing bounds check. T
In the Android kernel in the FingerTipS touchscreen driver there is a possible memory corruption due to a race condition
In the Android kernel in FingerTipS touchscreen driver there is a possible out of bounds read due to a missing bounds ch
In the Android kernel in the FingerTipS touchscreen driver there is a possible out of bounds write due to a missing boun
In the Android kernel in the FingerTipS touchscreen driver there is a possible use-after-free due to improper locking. T
In the Android kernel in the FingerTipS touchscreen driver there is a possible out of bounds write due to improper input
In the Android kernel in F2FS driver there is a possible out of bounds read due to a missing bounds check. This could le
In the Android kernel in sync debug fs driver there is a kernel pointer leak due to the usage of printf with %p. This co
In the Android kernel in the vl53L0 driver there is a possible out of bounds write due to a permissions bypass. This cou
In the Android kernel in the mnh driver there is possible memory corruption due to a use after free. This could lead to
In the Android kernel in the mnh driver there is a possible out of bounds write due to improper input validation. This c
In the Android kernel in the bootloader there is a possible secure boot bypass. This could lead to local escalation of p
In the Android kernel in Bluetooth there is a possible out of bounds write due to a missing bounds check. This could lea
In the Android kernel in sdcardfs there is a possible violation of the separation of data between profiles due to shared
In the Android kernel in the synaptics_dsx_htc touchscreen driver there is a possible out of bounds write due to a use a
In the Android kernel in the mnh driver there is a use after free due to improper locking. This could lead to escalation
In the Android kernel in the mnh driver there is a possible out of bounds write due to a missing bounds check. This coul
In the Android kernel in the synaptics_dsx_htc touchscreen driver there is a possible use after free due to improper loc
In the Android kernel in the mnh driver there is a race condition due to insufficient locking. This could lead to a use-
In the Android kernel in unifi and r8180 WiFi drivers there is a possible out of bounds write due to a missing bounds ch
In the Android kernel in the FingerTipS touchscreen driver there is a possible out of bounds write due to a missing boun
In the Android kernel in the f2fs driver there is a possible out of bounds read due to a missing bounds check. This coul
In the Android kernel in the kernel MMU code there is a possible execution path leaving some kernel text and rodata page
NVIDIA Tegra contains a vulnerability in BootRom where a user with kernel level privileges can write an arbitrary value
In readArgumentList of zygote.java in Android 10, there is a possible command injection due to improper input validation
In binder_transaction of binder.c in the Android kernel, there is a possible out of bounds write due to an integer overf
In ippSetValueTag of ipp.c in Android 8.0, 8.1 and 9, there is a possible out of bounds read due to improper input valid
In NDEF_MsgValidate of ndef_utils in Android 7.1.1, 7.1.2, 8.0, 8.1 and 9, there is a possible out of bounds read due to
In rw_t4t_sm_read_ndef of rw_t4t in Android 7.1.1, 7.1.2, 8.0, 8.1 and 9, there is a possible out of bounds write due to
In isPreferred of HidProfile.java in Android 7.1.1, 7.1.2, 8.0, 8.1 and 9, there is a possible device type confusion due
In ihevcd_parse_buffering_period_sei of ihevcd_parse_headers.c in Android 8.0, 8.1 and 9, there is a possible out of bou
In checkAccess of SliceManagerService.java in Android 9, there is a possible permissions check bypass due to incorrect o
In SensorManager::assertStateLocked of SensorManager.cpp in Android 7.1.1, 7.1.2, 8.0, 8.1, and 9, there is a possible u
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