Vulnerabilidades em Google

7.001 resultados
Aná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-2025-36934HIGHIn bigo_worker_thread of private/google-modules/video/gchips/bigo.c, there is a possible use after free due to a race condition. This could EPSS 0.1%CVE-2026-55317MEDIUMIn printf of printf.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local escalation of privEPSS 0.1%CVE-2025-48590MEDIUMIn verifyAndGetBypass of AppOpsService.java, there is a possible method for a malicious app to prevent dialing emergency services under limiEPSS 0.1%CVE-2025-26456MEDIUMIn multiple functions of DexUseManagerLocal.java, there is a possible way to crash system server due to a logic error in the code. This coulEPSS 0.1%CVE-2026-56932MEDIUMIn Trusted Execution Environment, there is a possible memory corruption due to improper input validation. This could lead to local escalatioEPSS 0.1%CVE-2025-48589HIGHIn multiple functions of HeaderPrivacyIconsController.kt, there is a possible way to grand permissions across user due to a logic error in EPSS 0.1%CVE-2026-57035MEDIUMIn multiple locations, there is a possible out-of-bounds write due to a missing bounds check. This could lead to local escalation of privileEPSS 0.1%CVE-2024-22010MEDIUMIn dvfs_plugin_caller of fvp.c, there is a possible out of bounds read due to a missing bounds check. This could lead to local information dEPSS 0.1%CVE-2017-13321MEDIUMIn SensorService::isDataInjectionEnabled of frameworks/native/services/sensorservice/SensorService.cpp, there is a possible out of bounds reEPSS 0.1%CVE-2025-48642MEDIUMIn jump_to_payload of payload.rs, there is a possible information disclosure due to a logic error in the code. This could lead to local infoEPSS 0.1%CVE-2025-48587MEDIUMIn multiple functions of ProfilingService.java, there is a possible persistent denial of service due to improper input validation. This coulEPSS 0.1%CVE-2026-56972MEDIUMIn multiple locations, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to local escalation of privEPSS 0.1%CVE-2025-32312HIGHIn createIntentsList of PackageParser.java , there is a possible way to bypass lazy bundle hardening, allowing modified data to be passed toEPSS 0.1%CVE-2026-0034HIGHIn setPackageOrComponentEnabled of ManagedServices.java, there is a possible notification policy desync due to improper input validation. ThEPSS 0.1%CVE-2026-56986HIGHIn multiple files, there is a possible out-of-bounds read due to type confusion. This could lead to local escalation of privilege with no adEPSS 0.1%CVE-2026-56985HIGHIn multiple files, there is a possible way to obtain signatures due to type confusion. This could lead to local escalation of privilege withEPSS 0.1%CVE-2025-22430MEDIUMIn isInSignificantPlace of multiple files, there is a possible way to access sensitive information due to a missing permission check. This cEPSS 0.1%CVE-2023-21381—In Media Resource Manager, there is a possible local arbitrary code execution due to use after free. This could lead to local escalation of EPSS 0.1%CVE-2026-58773MEDIUMIn link_load_gnss_image of link_device.c, there is a possible out-of-bounds write due to a missing bounds check. This could lead to local esEPSS 0.1%CVE-2023-21372—In libdexfile, there is a possible out of bounds read due to a missing bounds check. This could lead to local escalation of privilege with nEPSS 0.1%