16,977 known vulnerabilities
Top Products
In NFC server, there is a possible out of bounds read due to a missing bounds check. This could lead to local informatio
In libeffects, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code exe
In netd, there is a possible out of bounds read due to a use after free. This could lead to remote information disclosur
In the settings UI, there is a possible spoofing vulnerability due to a missing permission check. This could lead to a u
In libstagefright, there is a possible resource exhaustion due to a missing bounds check. This could lead to remote deni
In the Activity Manager service, there is a possible permission bypass due to incorrect permission check. This could lea
In FingerprintService, there is a possible bypass for operating system protections that isolate user profiles from each
In Account of Account.java, there is a possible boot loop due to improper input validation. This could lead to local den
In hostapd, there is a possible out of bounds write due to a race condition. This could lead to local escalation of priv
In JobStore, there is a mismatched serialization/deserialization for the "battery-not-low" job attribute. This could lea
In libskia, there is a possible crash due to a missing null check. This could lead to remote denial of service with no a
In libvpx, there is a possible resource exhaustion due to improper input validation. This could lead to remote denial of
In sonivox, there is a possible out of bounds read due to an incorrect bounds check. This could lead to remote informati
In Bluetooth, there is a use of uninitialized variable. This could lead to local information disclosure with no addition
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 libSBRdec there is a possible out of bounds read due to a missing bounds check. This could lead to remote information
In Bluetooth, there is a possible deserialization error due to missing string validation. This could lead to remote code
In AudioService, there is a possible trigger of background user audio due to a permissions bypass. This could lead to lo
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code exec
In libSACdec, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information di
In the TEE, there's a possible out of bounds read due to a missing bounds check. This could lead to local information di
In libavc there is a possible information disclosure due to uninitialized data. This could lead to remote information di
In NFC, there is a possible out of bounds write due to a missing bounds check. This could lead to a to local escalation
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In NFC server, there is a possible out of bounds read due to a missing bounds check. This could lead to local 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's a possible out of bounds read due to a missing bounds check. This could lead to information discl
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 SyncStatusObserver, there is a possible bypass for operating system protections that isolate user profiles from each
In Keymaster, there is a possible EoP due to a use after free. This could lead to local escalation of privilege with no
In libstagefright, there is a possible resource exhaustion due to improper input validation. This could lead to remote d
In libstagefright, there is a possible resource exhaustion due to improper input validation. This could lead to remote d
In the m4v_h263 codec, there is a possible out of bounds read due to a use after free. This could lead to local informat
In libstagefright, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote code
In NFC server, there is a possible out of bounds read due to a missing bounds check. This could lead to local informatio
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 Bluetooth, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informatio
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 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 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 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
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