16,977 known vulnerabilities
Top Products
Inappropriate implementation in iFrame Sandbox in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to bypas
Use after free in PDF Accessibility in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to potentially expl
Out of bounds read in WebAudio in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to potentially exploit h
Race in V8 in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to potentially exploit heap corruption via a
Inappropriate implementation in WebView in Google Chrome on Android prior to 95.0.4638.54 allowed a remote attacker to l
Inappropriate implementation in Blink in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to abuse content
Use after free in Profiles in Google Chrome prior to 95.0.4638.54 allowed a remote attacker who convinced a user to enga
Use after free in Network APIs in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to potentially exploit h
Heap buffer overflow in Settings in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to engage with Dev Too
Use after free in V8 in Google Chrome prior to 95.0.4638.54 allowed a remote attacker who had convinced a user to allow
Heap buffer overflow in PDFium in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to potentially exploit h
Use after free in Dev Tools in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to potentially exploit heap
Use after free in Incognito in Google Chrome prior to 95.0.4638.54 allowed a remote attacker to potentially exploit heap
Heap buffer overflow in Skia in Google Chrome prior to 95.0.4638.54 allowed a remote attacker who had compromised the re
Inappropriate implementation in Sandbox in Google Chrome prior to 94.0.4606.81 allowed a remote attacker to potentially
heap buffer overflow in WebRTC in Google Chrome prior to 94.0.4606.81 allowed a remote attacker who convinced a user to
Heap buffer overflow in Blink in Google Chrome prior to 94.0.4606.81 allowed a remote attacker to potentially exploit he
Use after free in Garbage Collection in Google Chrome prior to 94.0.4606.81 allowed a remote attacker to potentially exp
In bpf_skb_change_head of filter.c, there is a possible out of bounds read due to a use after free. This could lead to l
In TBD of TBD, there is a possible out of bounds write due to improper locking. This could lead to local escalation of p
In set_default_passthru_cfg of passthru.c, there is a possible out of bounds read due to a missing bounds check. This co
In memzero_explicit of compiler-clang.h, there is a possible bypass of defense in depth due to uninitialized data. This
In acc_read of f_accessory.c, there is a possible memory corruption due to a use after free. This could lead to local es
In ip6_xmit of ip6_output.c, there is a possible out of bounds write due to a use after free. This could lead to local e
In audio DSP, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalat
In audio DSP, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalat
In audio DSP, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalat
In display driver, there is a possible memory corruption due to uninitialized data. This could lead to local escalation
In display driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In wifi driver, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informat
In wifi driver, there is a possible system crash due to a missing bounds check. This could lead to remote denial of serv
In wifi driver, there is a possible system crash due to a missing bounds check. This could lead to remote denial of serv
In ccu, there is a possible memory corruption due to improper locking. This could lead to local escalation of privilege
In ape extractor, there is a possible out of bounds read due to a heap buffer overflow. This could lead to local informa
In ape extractor, there is a possible out of bounds read due to a heap buffer overflow. This could lead to local informa
In ape extractor, there is a possible out of bounds read due to a heap buffer overflow. This could lead to local informa
In flv extractor, there is a possible out of bounds read due to an integer overflow. This could lead to local informatio
In asf extractor, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local info
In asf extractor, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local info
In flv extractor, there is a possible out of bounds read due to a heap buffer overflow. This could lead to local informa
In flv extractor, there is a possible out of bounds read due to a missing bounds check. This could lead to local informa
In flv extractor, there is a possible out of bounds read due to a missing bounds check. This could lead to local informa
In flv extractor, there is a possible out of bounds read due to an integer overflow. This could lead to local informatio
In flv extractor, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local info
In flv extractor, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local info
Swift File Transfer Mobile v1.1.2 and below was discovered to contain a cross-site scripting (XSS) vulnerability via the
In RW_SetActivatedTagType of rw_main.cc, there is possible memory corruption due to a race condition. This could lead to
In runDumpHeap of ActivityManagerShellCommand.java, there is a possible deletion of system files due to a confused deput
In startListening of PluginManagerImpl.java, there is a possible way to disable arbitrary app components due to a missin
In sanitizeSbn of NotificationManagerService.java, there is a possible way to keep service running in foreground and kee
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