16,977 known vulnerabilities
Top Products
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
In libvpx, there is a possible information disclosure due to improper input validation. This could lead to remote inform
In Bluetooth, there is a possible out of bounds read due to improper input validation. This could lead to remote informa
In Bluetooth, there is a possible out of bounds read due to a use after free. This could lead to remote information disc
In Bluetooth, there is a possible null pointer dereference due to a missing null check. This could lead to remote denial
In profman, there is a possible out of bounds write due to memory corruption. This could lead to local escalation of pri
In the Framework, it is possible to set up BROWSEABLE intents to take over certain URLs. This could lead to remote infor
In Bluetooth, there is a possible information disclosure due to a use after free. This could lead to local information d
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote denial of
In the Screen Lock, there is a possible information disclosure due to an unusual root cause. In certain circumstances, t
In opencv calls that use libpng, there is a possible out of bounds write due to a missing bounds check. This could lead
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
In libandroidfw, there is a possible OOB read due to an integer overflow. This could lead to local information disclosur
In libhevc, there is a possible out of bounds read due to an integer overflow. This could lead to remote denial of servi
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
In libstagefright, there is a possible resource exhaustion due to a missing bounds check. This could lead to remote deni
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to local information
In libstagefright there is a possible information disclosure due to uninitialized data. This could lead to remote inform
In libstagefright there is a possible information disclosure due to uninitialized data. This could lead to remote inform
In wpa_supplicant, there is a possible man in the middle vulnerability due to improper input validation of the basicCons
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
In libSBRdec there is a possible out of bounds read due to incorrect bounds check. This could lead to remote information
In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information di
In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information di
In libhevc there is a possible information disclosure due to uninitialized data. This could lead to remote information d
In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information di
In notification management of the service manager, there is a possible permissions bypass. This could lead to local esca
In libhevc there is a possible information disclosure due to uninitialized data. This could lead to remote information d
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In cn-cbor, there is a possible out of bounds read due to improper casting. This could lead to remote information disclo
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In Bluetooth, there is a possible null pointer dereference due to a missing null check. This could lead to remote denial
The Print Service is susceptible to man in the middle attacks due to improperly used crypto. This could lead to remote i
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In Bluetooth, there is possible controlled termination due to a missing bounds check. This could lead to remote denial o
In libxaac, there is a possible out of bounds read due to uninitialized data. This could lead to information disclosure
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote denial of
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote denial of
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
In Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
In NFC server, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In libxaac, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information
In LockPatternUtils, there is a possible escalation of privilege due to an improper permissions check. This could lead t
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