16,977 known vulnerabilities
Top Products
When Bazel Plugin in intellij imports a project (either using "import project" or "Auto import") the dialog for trusting
In plugin_ipc_handler of slc_plugin.c, there is a possible information disclosure due to uninitialized data. This could
In gpu_slc_get_region of pixel_gpu_slc.c, there is a possible EoP due to a use after free. This could lead to local esca
there is a possible information disclosure due to side channel information disclosure. This could lead to local informat
In dhd_prot_txstatus_process of dhd_msgbuf.c, there is a possible out of bounds write due to a missing bounds check. Thi
In DeregAcceptProcINT of cn_NrmmStateDeregInit.cpp, there is a possible denial of service due to a logic error in the co
there is a possible cellular denial of service due to a logic error in the code. This could lead to remote denial of ser
In gpu_pm_power_on_top_nolock of pixel_gpu_power.c, there is a possible compromise of protected memory due to a logic er
In lwis_initialize_transaction_fences of lwis_fence.c, there is a possible out of bounds write due to a missing bounds c
In set_secure_reg of sac_handler.c, there is a possible out of bounds read due to a missing bounds check. This could lea
In lwis_add_completion_fence of lwis_fence.c, there is a possible escalation of privilege due to type confusion. This co
Permission Bypass allowing attackers to disable HDCP 2.2 encryption by not completing the HDCP Key Exchange initializat
In pl330_dma_from_peri_start() of fp_spi_dma.c, there is a possible out of bounds write due to a missing bounds check. T
In fvp_freq_histogram_init of fvp.c, there is a possible Information Disclosure due to uninitialized data. This could le
In CellInfoListParserV2::FillCellInfo() of protocolnetadapter.cpp, there is a possible out of bounds read due to a missi
In tpu_get_int_state of tpu.c, there is a possible information disclosure due to uninitialized data. This could lead to
In wl_notify_rx_mgmt_frame of wl_cfg80211.c, there is a possible out of bounds write due to an integer overflow. This co
there is a possible persistent Denial of Service due to test/debugging code left in a production build. This could lead
There is a possible escalation of privilege due to improperly used crypto. This could lead to remote escalation of privi
In handle_msg_shm_map_req of trusty/user/base/lib/spi/srv/tipc/tipc.c, there is a possible stack data disclosure due to
In handle_msg of main.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to loc
In sec_media_protect of media.c, there is a possible permission bypass due to a race condition. This could lead to local
In memcall_add of memlog.c, there is a possible buffer overflow due to improper input validation. This could lead to loc
In AcvpOnMessage of avcp.cpp, there is a possible EOP due to uninitialized data. This could lead to local escalation of
In circ_read of link_device_memory_legacy.c, there is a possible out of bounds write due to an incorrect bounds check. T
In ProtocolVsimOperationAdapter() of protocolvsimadapter.cpp, there is a possible out of bounds read due to a missing bo
In prepare_response_locked of lwis_transaction.c, there is a possible out of bounds write due to improper input validati
Remote prevention of access to cellular service with no user interaction (for example, crashing the cellular radio servi
In v4l2_smfc_qbuf of smfc-v4l2-ioctls.c, there is a possible out of bounds write due to a missing bounds check. This cou
In lwis_fence_signal of lwis_debug.c, there is a possible Use after Free due to improper locking. This could lead to loc
In gpu_pm_power_off_top_nolock of pixel_gpu_power.c, there is a possible compromise of protected memory due to a race co
In ProtocolCellIdentityParserV4::Parse() of protocolnetadapter.cpp, there is a possible out of bounds read due to a miss
In ProtocolCdmaCallWaitingIndAdapter::GetCwInfo() of protocolsmsadapter.cpp, there is a possible out of bounds read due
there is a possible way to bypass due to a logic error in the code. This could lead to local escalation of privilege wi
In BCMFASTPATH of dhd_msgbuf.c, there is a possible out of bounds write due to a missing bounds check. This could lead t
In bc_get_converted_received_bearer of bc_utilities.c, there is a possible out of bounds read due to a missing bounds ch
In _s5e9865_mif_set_rate of exynos_dvfs.c, there is a possible out of bounds read due to improper casting. This could le
In handle_init of goodix/main/main.c, there is a possible memory corruption due to type confusion. This could lead to lo
In sec_media_unprotect of media.c, there is a possible memory corruption due to a race condition. This could lead to loc
In lwis_process_transactions_in_queue of lwis_transaction.c, there is a possible use after free due to a use after free.
In pktproc_fill_data_addr_without_bm of link_rx_pktproc.c, there is a possible out of bounds write due to a missing boun
In aur_get_state of aurora.c, there is a possible information disclosure due to uninitialized data. This could lead to l
In prepare_response of lwis_periodic_io.c, there is a possible out of bounds write due to an integer overflow. This coul
In ss_AnalyzeOssReturnResUssdArgIe of ss_OssAsnManagement.c, there is a possible out of bounds read due to improper inpu
In hwbcc_ns_deprivilege of trusty/user/base/lib/hwbcc/client/hwbcc.c, there is a possible uninitialized stack data discl
In ProtocolPsDedicatedBearInfoAdapter::processQosSession of protocolpsadapter.cpp, there is a possible out of bounds rea
Use after free in PDFium in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap c
Use after free in PDFium in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap c
Use after free in Audio in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap co
Heap buffer overflow in Tab Strip in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to perform an out of
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