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-2025-0083MEDIUMIn multiple locations, there is a possible way to access content across user profiles due to URI double encoding. This could lead to local iEPSS 0.1%CVE-2025-22413MEDIUMIn multiple functions of hyp-main.c, there is a possible privilege escalation due to a logic error in the code. This could lead to local infEPSS 0.1%CVE-2024-34737HIGHIn ensureSetPipAspectRatioQuotaTracker of ActivityClientController.java, there is a possible way to generate unmovable and undeletable pip wEPSS 0.1%CVE-2023-40141—In temp_residency_name_store of thermal_metrics.c, there is a possible out of bounds write due to a missing bounds check. This could lead toEPSS 0.1%CVE-2025-22433HIGHIn canForward of IntentForwarderActivity.java, there is a possible bypass of the cross profile intent filter most commonly used in Work ProfEPSS 0.1%CVE-2023-21299—In Package Manager, there is a possible way to determine whether an app is installed, without query permissions, due to side channel informaEPSS 0.1%CVE-2025-26425MEDIUMIn multiple functions of RoleService.java, there is a possible permission squatting vulnerability due to a logic error in the code. This couEPSS 0.1%CVE-2025-48540HIGHIn processTransactInternal of RpcState.cpp, there is a possible local out of memory write due to a logic error in the code. This could lead EPSS 0.1%CVE-2023-40137—In multiple functions of DialogFillUi.java, there is a possible way to view another user's images due to a confused deputy. This could lead EPSS 0.1%CVE-2025-26455HIGHIn multiple functions of NdkMediaCodec.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local EPSS 0.1%CVE-2025-48630HIGHIn drawLayersInternal of SkiaRenderEngine.cpp, there is a possible way to access the GPU cache due to side channel information disclosure. TEPSS 0.1%CVE-2017-13323HIGHIn String16 of String16.cpp, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privEPSS 0.1%CVE-2026-0013HIGHIn setupLayout of PickActivity.java, there is a possible way to start any activity as a DocumentsUI app due to a confused deputy. This couldEPSS 0.1%CVE-2023-21303—In Content, here is a possible way to determine whether an app is installed, without query permissions, due to side channel information discEPSS 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-2024-53841HIGHIn startListeningForDeviceStateChanges, there is a possible Permission Bypass due to a confused deputy. This could lead to local escalation EPSS 0.1%CVE-2024-32908HIGHIn sec_media_protect of media.c, there is a possible permission bypass due to a race condition. This could lead to local escalation of priviEPSS 0.1%CVE-2024-23710HIGHIn assertPackageWithSharedUserIdIsPrivileged of InstallPackageHelper.java, there is a possible execution of arbitrary app code as a privilegEPSS 0.1%CVE-2023-21276—In writeToParcel of CursorWindow.cpp, there is a possible information disclosure due to uninitialized data. This could lead to local informaEPSS 0.1%CVE-2018-9372HIGHIn cmd_flash_mmc_sparse_img of dl_commands.c, there is a possible out of bounds write due to a missing bounds check. This could lead to a loEPSS 0.1%