Vulnerabilidades em google
7.001 resultadosAnálise Vexday
Google registra presença mínima no panorama de risco com apenas 4 vulnerabilidades na base, nenhuma sob exploração ativa (KEV) e apenas 1 crítica identificada. A fraqueza dominante relaciona-se a validação inadequada de entrada (CWE-20), indicando risco controlado e sem pressão temporal dado que não há publicações nos últimos 90 dias.
CVE-2026-17870MEDIUMInsufficient validation of untrusted input in Cast in Google Chrome prior to 151.0.7922.72 allowed an attacker on the local network segment EPSS 0.2%CVE-2024-44097CRITICALAccording to the researcher: "The TLS connections are encrypted against tampering or eavesdropping. However, the application does not validaEPSS 0.2%CVE-2026-7961MEDIUMInsufficient validation of untrusted input in Permissions in Google Chrome prior to 148.0.7778.96 allowed an attacker on the local network sEPSS 0.2%CVE-2026-13879MEDIUMUse after free in Bluetooth in Google Chrome prior to 150.0.7871.47 allowed an attacker on the local network segment to obtain potentially sEPSS 0.2%CVE-2026-14119MEDIUMType Confusion in Bluetooth in Google Chrome on Windows prior to 150.0.7871.47 allowed an attacker on the local network segment to obtain poEPSS 0.2%CVE-2026-14048MEDIUMUse after free in Chromecast in Google Chrome prior to 150.0.7871.47 allowed an attacker on the local network segment to obtain potentially EPSS 0.2%CVE-2023-21342HIGHIn RemoteSpeechRecognitionService of RemoteSpeechRecognitionService.java, there is a possible way to launch an activity from the background EPSS 0.2%CVE-2025-1079HIGHRCE In Google Web DesignerEPSS 0.2%CVE-2026-0037HIGHIn multiple functions of ffa.c, there is a possible memory corruption due to a logic error in the code. This could lead to local escalation EPSS 0.2%CVE-2026-106253MEDIUMIncorrect authorization in Extensions in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to obtain cross-origin data via a crEPSS 0.2%CVE-2026-0030HIGHIn __host_check_page_state_range of mem_protect.c, there is a possible out of bounds write due to an incorrect bounds check. This could leadEPSS 0.2%CVE-2026-0063CRITICALIn setAllowedCarriers of PhoneInterfaceManager.java, there is a possible way to disable carrier restrictions due to a logic error in the codEPSS 0.2%CVE-2026-0071CRITICALIn SettingsLib, there is a possible missing permission check due to a logic error in the code. This could lead to local escalation of privilEPSS 0.2%CVE-2026-0031HIGHIn multiple functions of mem_protect.c, there is a possible out of bounds write due to an integer overflow. This could lead to local escalatEPSS 0.2%CVE-2026-106402MEDIUMIncorrect authorization in Extensions in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to spoEPSS 0.2%CVE-2026-0028HIGHIn __pkvm_host_share_guest of mem_protect.c, there is a possible out of bounds write due to an integer overflow. This could lead to local esEPSS 0.2%CVE-2026-12032LOWInappropriate implementation in Passwords in Google Chrome on Android prior to 149.0.7827.115 allowed a remote attacker who had compromised EPSS 0.2%CVE-2026-11219MEDIUMInappropriate implementation in Navigation in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass navigation restrictioEPSS 0.2%CVE-2026-11228MEDIUMInappropriate implementation in File Input in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage EPSS 0.2%CVE-2026-11300MEDIUMInappropriate implementation in Permissions in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to perform UI spoofing via a cEPSS 0.2%