Vulnerabilidades em Google
5.229 resultadosAnálise 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-2018-9384MEDIUMIn multiple locations, there is a possible way to bypass KASLR due to an unusual root cause. This could lead to local information disclosureEPSS 0.1%CVE-2026-0005MEDIUMIn onServiceDisconnected of KeyguardServiceDelegate.java, there is a possible partial bypass of app pinning allowing limited interaction witEPSS 0.1%CVE-2024-31332HIGHIn multiple locations, there is a possible way to bypass a restriction on adding new Wi-Fi connections due to a missing permission check. ThEPSS 0.1%CVE-2023-21344—In Job Scheduler, there is a possible way to determine whether an app is installed, without query permissions, due to side channel informatiEPSS 0.1%CVE-2025-48598MEDIUMIn multiple locations, there is a possible way to alter the primary user's face unlock settings due to a confused deputy. This could lead toEPSS 0.1%CVE-2026-8586MEDIUMInappropriate implementation in Chromoting in Google Chrome prior to 148.0.7778.168 allowed a local attacker to bypass discretionary access EPSS 0.1%CVE-2023-40110MEDIUMIn multiple functions of MtpPacket.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escaEPSS 0.1%CVE-2018-9387HIGHIn multiple functions of mnh-sm.c, there is a possible way to trigger a heap overflow due to an integer overflow. This could lead to local eEPSS 0.1%CVE-2024-0027MEDIUMIn multiple functions of SnoozeHelper.java, there is a possible way to cause a boot loop due to resource exhaustion. This could lead to locaEPSS 0.1%CVE-2024-0052MEDIUMIn multiple functions of healthconnect, there is a possible leakage of exercise route data due to a missing permission check. This could leaEPSS 0.1%CVE-2026-0035HIGHIn createRequest of MediaProvider.java, there is a possible way for an app to gain read/write access to non-existing files due to a logic erEPSS 0.1%CVE-2023-21333—In Text Services, there is a possible way to determine whether an app is installed, without query permissions, due to side channel informatiEPSS 0.1%CVE-2023-40117HIGHIn resetSettingsLocked of SettingsProvider.java, there is a possible lockscreen bypass due to a permissions bypass. This could lead to localEPSS 0.1%CVE-2024-31322MEDIUMIn updateServicesLocked of AccessibilityManagerService.java, there is a possible way for an app to be hidden from the Setting while retaininEPSS 0.1%CVE-2018-9405MEDIUMIn BnDmAgent::onTransact of dm_agent.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to local esEPSS 0.1%CVE-2026-5889MEDIUMCryptographic Flaw in PDFium in Google Chrome prior to 147.0.7727.55 allowed an attacker to read potentially sensitive information from encrEPSS 0.1%CVE-2024-23715HIGHIn PMRWritePMPageList of pmr.c, there is a possible out of bounds write due to a logic error in the code. This could lead to local escalatioEPSS 0.1%CVE-2024-0019MEDIUMIn setListening of AppOpsControllerImpl.java, there is a possible way to hide the microphone privacy indicator when restarting systemUI due EPSS 0.1%CVE-2024-31323HIGHIn onCreate of multiple files, there is a possible way to trick the user into granting health permissions due to tapjacking. This could leadEPSS 0.1%CVE-2024-31313HIGHIn availableToWriteBytes of MessageQueueBase.h, there is a possible out of bounds write due to an incorrect bounds check. This could lead toEPSS 0.1%