16,977 known vulnerabilities
Top Products
In gpu_slc_liveness_update of pixel_gpu_slc.c, there is a possible out of bounds read due to a missing bounds check. Thi
In SAEMM_DiscloseGuti of SAEMM_RadioMessageCodec.c, there is a possible out of bounds read due to a missing bounds check
In pt_sysctl_command of pt.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead
In ppmp_unprotect_buf of drm_fw.c, there is a possible compromise of protected memory due to a logic error in the code.
In bigo_unlocked_ioctl of bigo.c, there is a possible UAF due to a missing bounds check. This could lead to local escala
In dumpBatteryDefend of dump_power.cpp, there is a possible out of bounds read due to a heap buffer overflow. This could
In ss_ProcessRejectComponent of ss_MmConManagement.c, there is a possible out of bounds read due to a missing bounds che
In dvfs_plugin_caller of fvp.c, there is a possible out of bounds read due to a missing bounds check. This could lead to
In init_data of , there is a possible out of bounds write due to a missing bounds check. This could lead to local escala
In config_gov_time_windows of tmu.c, there is a possible out of bounds write due to a missing bounds check. This could l
In constraint_check of fvp.c, there is a possible out of bounds read due to a missing bounds check. This could lead to l
OOB read in the TMU plugin that allows for memory disclosure in the power management subsystem of the device.
there is a possible Authentication Bypass due to improperly used crypto. This could lead to local escalation of privileg
In access_secure_service_from_temp_bond of btm_sec.cc, there is a possible way to achieve keystroke injection due to imp
In getCustomPrinterIcon of PrintManagerService.java, there is a possible way to view other user's images due to a confus
In multiple functions of healthconnect, there is a possible leakage of exercise route data due to a missing permission c
In onQueueFilled of SoftMPEG4.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lea
In getConfig of SoftVideoDecoderOMXComponent.cpp, there is a possible out of bounds write due to a missing validation ch
In multiple locations, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local e
In Session of AccountManagerService.java, there is a possible method to retain foreground service privileges due to inco
In writeUserLP of UserManagerService.java, device policies are serialized with an incorrect tag due to a logic error in
In installExistingPackageAsUser of InstallPackageHelper.java, there is a possible carrier restriction bypass due to a lo
In smp_proc_sec_req of smp_act.cc, there is a possible out of bounds read due to improper input validation. This could l
In createSessionInternal of PackageInstallerService.java, there is a possible run-as any app due to improper input valid
In attp_build_value_cmd of att_protocol.cc, there is a possible out of bounds write due to a missing bounds check. This
Use after free in FedCM in Google Chrome prior to 122.0.6261.111 allowed a remote attacker to potentially exploit heap c
Inappropriate implementation in V8 in Google Chrome prior to 122.0.6261.111 allowed a remote attacker to potentially exp
Out of bounds memory access in V8 in Google Chrome prior to 122.0.6261.111 allowed a remote attacker to perform out of b
Improper access control in Samsung Voice Recorder prior to versions 21.5.16.01 in Android 12 and Android 13, 21.4.51.02
Improper access control in Samsung Voice Recorder prior to versions 21.5.16.01 in Android 12 and Android 13, 21.4.51.02
In pq, there is a possible out of bounds read due to an incorrect bounds check. This could lead to local information dis
In pq, there is a possible write-what-where condition due to an incorrect bounds check. This could lead to local escalat
In vdec, there is a possible permission bypass due to a permissions bypass. This could lead to local information disclos
In battery, there is a possible escalation of privilege due to a missing bounds check. This could lead to local escalati
In nvram, there is a possible information disclosure due to a missing bounds check. This could lead to local information
In aee, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of
In da, there is a possible out of bounds write due to lack of valudation. This could lead to local escalation of privile
In da, there is a possible information disclosure due to improper input validation. This could lead to local information
In wlan firmware, there is a possible out of bounds write due to improper input validation. This could lead to local esc
In da, there is a possible out of bounds write due to lack of valudation. This could lead to local escalation of privile
In da, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of
In da, there is a possible information disclosure due to improper input validation. This could lead to local information
In da, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privil
In flashc, there is a possible out of bounds write due to lack of valudation. This could lead to local escalation of pri
In flashc, there is a possible out of bounds write due to lack of valudation. This could lead to local escalation of pri
In lk, there is a possible escalation of privilege due to a missing bounds check. This could lead to local escalation of
In OPTEE, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local information
In da, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of p
Type Confusion in V8 in Google Chrome prior to 122.0.6261.94 allowed a remote attacker to potentially exploit heap corru
Type Confusion in V8 in Google Chrome prior to 122.0.6261.94 allowed a remote attacker to potentially exploit object cor
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