Vulnerabilidades en Google
5229 resultadosAnálisis Vexday
Com 4.763 CVEs catalogadas e 77 confirmadas em exploração ativa pelo CISA KEV, a taxa de exploração dos produtos Google é 3,6 vezes superior à média geral do catálogo, sinalizando risco operacional elevado para organizações que dependem desse ecossistema. O volume de 1.225 CVEs surgidas nos últimos 90 dias indica cadência intensa de descobertas, exigindo ciclos de patching ágeis. O tipo de falha mais recorrente é CWE-416 (use-after-free), classe de vulnerabilidade que frequentemente viabiliza execução de código arbitrário e escalada de privilégios. Destaque especial para CVE-2023-4863, com EPSS de 0,9974 — valor próximo ao máximo possível —, indicando probabilidade altíssima de exploração ativa e merecendo tratamento prioritário imediato.
CVE-2026-13991MEDIUMInsufficient validation of untrusted input in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker to perEPSS 0.2%CVE-2026-15124MEDIUMInsufficient policy enforcement in Passwords in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to bypass same origin policyEPSS 0.2%CVE-2025-13992MEDIUMSide-channel information leakage in Navigation and Loading in Google Chrome prior to 139.0.7258.66 allowed a remote attacker to bypass site EPSS 0.2%CVE-2024-40676HIGHIn checkKeyIntent of AccountManagerService.java, there is a possible way to bypass intent security check and install an unknown app due to aEPSS 0.2%CVE-2023-21272—In readFrom of Uri.java, there is a possible bad URI permission grant due to improper input validation. This could lead to local escalation EPSS 0.2%CVE-2018-9471CRITICALIn the deserialization constructor of NanoAppFilter.java, there is a possible loss of data due to type confusion. This could lead to local eEPSS 0.2%CVE-2026-11127MEDIUMInappropriate implementation in WebAPKs in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to perform domain spoofEPSS 0.2%CVE-2026-11266MEDIUMInappropriate implementation in SafeBrowsing in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass Safe Browsing via aEPSS 0.2%CVE-2026-0904MEDIUMIncorrect security UI in Digital Credentials in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform domain spoofing viEPSS 0.2%CVE-2026-0129LOWIn RtcpByePacket::decodeByePacket, there is a possible due to a missing bounds check. This could lead to remote information disclosure withEPSS 0.2%CVE-2023-21284—In multiple functions of DevicePolicyManager.java, there is a possible way to prevent enabling the Find my Device feature due to improper inEPSS 0.2%CVE-2026-14105CRITICALInsufficient policy enforcement in Speech in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to bypass same origin policy viaEPSS 0.2%CVE-2023-21288—In visitUris of Notification.java, there is a possible way to reveal images across users due to a missing permission check. This could lead EPSS 0.2%CVE-2026-12022HIGHRace in Safe Browsing in Google Chrome on Mac prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to EPSS 0.2%CVE-2026-11026MEDIUMInappropriate implementation in Extensions in Google Chrome prior to 149.0.7827.53 allowed an attacker who convinced a user to install a malEPSS 0.2%CVE-2026-13822MEDIUMInappropriate implementation in Extensions in Google Chrome on Android prior to 150.0.7871.47 allowed an attacker who convinced a user to inEPSS 0.2%CVE-2024-32900CRITICALIn lwis_fence_signal of lwis_debug.c, there is a possible Use after Free due to improper locking. This could lead to local escalation of priEPSS 0.2%CVE-2025-36895HIGHInformation disclosureEPSS 0.2%CVE-2023-21392—In Bluetooth, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege when conneEPSS 0.2%CVE-2026-8520HIGHRace in Payments in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTEPSS 0.2%