16,977 known vulnerabilities
Top Products
Insufficient policy enforcement in Intents in Google Chrome on Android prior to 111.0.5563.64 allowed a remote attacker
Use after free in Core in Google Chrome on Lacros prior to 111.0.5563.64 allowed a remote attacker who convinced a user
Insufficient policy enforcement in Web Payments API in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to
Insufficient policy enforcement in Navigation in Google Chrome on iOS prior to 111.0.5563.64 allowed a remote attacker t
Insufficient policy enforcement in Web Payments API in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to
Insufficient policy enforcement in Autofill in Google Chrome on Android prior to 111.0.5563.64 allowed a remote attacker
Heap buffer overflow in Web Audio API in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to potentially e
Insufficient policy enforcement in Extensions API in Google Chrome prior to 111.0.5563.64 allowed an attacker who convin
Heap buffer overflow in UMA in Google Chrome prior to 111.0.5563.64 allowed a remote attacker who had compromised the re
Heap buffer overflow in Metrics in Google Chrome prior to 111.0.5563.64 allowed a remote attacker who had compromised th
Use after free in WebRTC in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to potentially exploit heap c
Stack buffer overflow in Crash reporting in Google Chrome on Windows prior to 111.0.5563.64 allowed a remote attacker wh
Use after free in DevTools in Google Chrome prior to 111.0.5563.64 allowed a remote attacker who had convienced the user
Type confusion in CSS in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to potentially exploit heap corr
Type confusion in V8 in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to potentially exploit heap corru
Use after free in Swiftshader in Google Chrome prior to 111.0.5563.64 allowed a remote attacker to potentially exploit h
In apu, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In apu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In ril, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In ril, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In ril, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In ril, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In ril, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In display drm, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In keyinstall, there is a possible information disclosure due to an integer overflow. This could lead to local informati
In widevine, there is a possible out of bounds write due to improper input validation. This could lead to local escalati
In usb, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In usb, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In usb, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In thermal, there is a possible memory corruption due to an uncaught exception. This could lead to local escalation of p
In pqframework, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In msdc, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation o
In adsp, there is a possible double free due to a race condition. This could lead to local escalation of privilege with
In vow, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In ion, there is a possible escalation of privilege due to improper locking. This could lead to local escalation of priv
In tinysys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In adsp, there is a possible escalation of privilege due to a logic error. This could lead to local escalation of privil
The YouTube Embedded 1.2 SDK binds to a service within the YouTube Main App. After binding, a remote context is created
In dropFramesUntilIframe of AAVCAssembler.cpp, there is a possible out of bounds read due to a heap buffer overflow. Thi
In onStart of BluetoothSwitchPreferenceController.java, there is a possible permission bypass due to a confused deputy.
In phNciNfc_MfCreateXchgDataHdr of phNxpExtns_MifareStd.cpp, there is a possible out of bounds write due to a missing bo
In run of ChooseTypeAndAccountActivity.java, there is a possible escalation of privilege due to unsafe deserialization.
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