16,977 known vulnerabilities
Top Products
In MediaProvider, there is a possible permissions bypass due to SQL injection. This could lead to local information disc
In NetworkStatsService, there is a possible access to protected data due to a missing permission check. This could lead
In DisplayManager, there is a possible permission bypass due to a missing permission check. This could lead to local esc
In libcodec2_soft_mp3dec, there is a possible information disclosure due to uninitialized data. This could lead to remot
In checkKeyIntent of AccountManagerService.java, there is a possible permission bypass. This could lead to local informa
In MediaProvider, there is a possible bypass of a permissions check due to a confused deputy. This could lead to local i
In SurfaceFlinger, there is possible memory corruption due to type confusion. This could lead to local escalation of pri
In UrlQuerySanitizer, there is a possible improper input validation. This could lead to remote code execution with no ad
In libstagefright, there is a possible dead loop due to an uncaught exception. This could lead to remote denial of servi
In iorap, there is a possible memory corruption due to a use after free. This could lead to local escalation of privileg
In the OMX encoder, there is a possible out of bounds read due to invalid input validation. This could lead to local inf
In the camera, there is a possible out of bounds read due to an integer overflow. This could lead to local information d
In libsonivox, there is a possible out of bounds read due to a missing bounds check. This could lead to remote informati
In libavb, there is a possible out of bounds read due to a missing bounds check. This could lead to local information di
In apexd, there is a possible out of bounds read due to a missing bounds check. This could lead to local information dis
In the mp3 extractor, there is a possible out of bounds write due to uninitialized data. This could lead to remote code
In libstagefright, there is a possible resource exhaustion due to improper input validation. This could lead to remote d
In UsageStatsManager, there is a possible access to protected data due to a missing permission check. This could lead to
In AudioService, there are missing permission checks. This could lead to local information disclosure of audio configura
In Battery Saver, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local informa
In Window Manager, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local inform
In LLVM, there is a possible ineffective stack cookie placement due to stack frame double reservation. This could lead t
In the Media extractor, there is a possible use after free due to improper locking. This could lead to remote code execu
In libstagefright, there is a possible resource exhaustion due to improper input validation. This could lead to remote d
In devicepolicy service, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local
In ADB server and USB server, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to l
In Java network APIs, there is possible access to sensitive network state due to a missing permission check. This could
In PackageManager, there is a missing permission check. This could lead to local information disclosure across users wit
In PackageManager, there is a missing permission check. This could lead to local information disclosure across users wit
In PackageManager, there is a missing permission check. This could lead to local information disclosure across user boun
In libmkvextractor, there is a possible resource exhaustion due to a missing bounds check. This could lead to remote den
In the AAC parser, there is a possible out of bounds read due to a missing bounds check. This could lead to remote infor
In NetworkPolicyManagerService, there is a possible permissions bypass due to a missing permission check. This could lea
In MediaProvider, there is a possible way to access ContentResolver and MediaStore entries the app shouldn't have access
In the OMX parser, there is a possible information disclosure due to a returned raw pointer. This could lead to local in
In tremolo, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information
In WindowManager, there is a possible launch of an unexpected app due to a confused deputy. This could lead to local esc
In factory reset protection, there is a possible FRP bypass due to a missing permission check. This could lead to local
In libstagefright, there is a possible out of bounds write due to an integer overflow. This could lead to remote code ex
In screencap, there is a possible command injection due to improper input validation. This could lead to local escalatio
In mediadrm, there is a possible out of bounds read due to a missing bounds check. This could lead to local information
In Pixel's use of the Catpipe library, there is possible memory corruption due to a use after free. This could lead to l
In blk_mq_queue_tag_busy_iter of blk-mq-tag.c, there is a possible use after free due to improper locking. This could le
In skb_to_mamac of networking.c, there is a possible out of bounds write due to an integer overflow. This could lead to
In kbd_keycode of keyboard.c, there is a possible out of bounds write due to a missing bounds check. This could lead to
In skb_headlen of /include/linux/skbuff.h, there is a possible out of bounds read due to memory corruption. This could l
In l2tp_session_delete and related functions of l2tp_core.c, there is possible memory corruption due to a use after free
In CamX code, there is a possible use after free due to a race condition. This could lead to local escalation of privile
In create_pinctrl of core.c, there is a possible out of bounds read due to a use after free. This could lead to local in
In the FPC TrustZone fingerprint App, there is a possible invalid command handler due to an exposed test feature. This c
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