CVE-20XX-?
agent?

Google Android CVEs.

Published CVEs affecting Google Android, ranked by exploit odds.

39 CVEs · updated 2026-11-19 01:02 UTC

Reset all
  1. CVE-2026-59007

    In decode_packed_entry_number of codebook.c, there is a possible out-of-bounds read due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    5.3 MEDIUM 0.2% exploit odds Fix listed
  2. CVE-2026-58924

    The vulnerability is a heap out-of-bounds read in the EVS HAL's `getStreamList()` method. An attacker can craft a `CameraDesc.metadata` byte array, which is parsed without validation, leading to an out-of-bounds read at an attacker-controlled offset within the HAL process's heap. The read data is then exfiltrated back to the attacker, potentially leaking sensitive information like pointers and buffer handles.

    Memory safety Device Google Android

    7.5 HIGH 0.2% exploit odds Fix listed
  3. CVE-2026-28645

    In onStrongAuthRequiredChanged of UsbService.java, there is a possible unauthenticated enabling of USB data due to a logic error in the code. This could lead to physical escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    6.8 MEDIUM 0.1% exploit odds Fix listed
  4. CVE-2026-49906

    An unprivileged application can bypass the `android.car.permission.CAR_DISPLAY_IN_CLUSTER` permission by registering an activity with the `android.car.cluster.NAVIGATION` category and requesting navigation app focus. The privileged `ClusterHomeSample` application, acting as a confused deputy, resolves and launches this arbitrary third-party activity on the safety-critical instrument cluster display without enforcing the necessary permission check, allowing for persistent display of potentially misleading or distracting content.

    Other Device Google Android

    7.8 HIGH 0.1% exploit odds Fix listed
  5. CVE-2026-49903

    The `ClusterRenderingService.dump()` method, accessible to processes holding `android.permission.DUMP` and `android.permission.PACKAGE_USAGE_STATS`, acts as a confused deputy. It allows attackers to write arbitrary values to `Settings.Global.OVERLAY_DISPLAY_DEVICES`, an operation normally requiring `android.permission.WRITE_SECURE_SETTINGS`, enabling persistent creation of system overlay displays and injection of key events into the cluster UI.

    Other Device Google Android

    5.5 MEDIUM 0.1% exploit odds Fix listed
  6. CVE-2026-58915

    A physical occupant on an Android Automotive OS (AAOS) Multi-User Multi-Display (MUMD) passenger display can view sensitive Heads-Up Notification (HUN) content and execute actions for a secure passenger user (User N) without authenticating. This bypasses the PassengerKeyguard because the HUN system only checks the global keyguard state, which is tied to the driver's unlocked display, and the PassengerKeyguard implementation fails to suppress HUNs or intercept action PendingIntents. Consequently, private notification data is disclosed, and user-N actions are executed without credential verification.

    Auth & access Device Google Android

    6.1 MEDIUM 0.1% exploit odds Fix listed
  7. CVE-2026-59044

    In multiple locations, there is a possible use-after-free due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  8. CVE-2026-59002

    In handleMessage of UsbDeviceManager.java, there is a possible lock-screen bypass due to a logic error in the code. This could lead to physical information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Disclosure Device Google Android

    4.6 MEDIUM 0.1% exploit odds Fix listed
  9. CVE-2026-58925

    The report details a heap Use-After-Free (UAF) vulnerability within the `android.hardware.automotive.evs-default` HAL service, stemming from unsynchronized access to an `std::unordered_map`. An unprivileged application with access to the EVS manager can trigger this UAF by making concurrent calls to `setExtendedInfo` and `getExtendedInfo`, potentially enabling code execution within the privileged HAL process.

    Memory safety Device Google Android

    7.8 HIGH 0.1% exploit odds Fix listed
  10. CVE-2026-59028

    In resolveAidConflictLocked of RegisteredAidCache.java, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  11. CVE-2026-59045

    In multiple locations, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    7.4 HIGH 0.1% exploit odds Fix listed
  12. CVE-2026-55289

    In multiple functions in multiple locations, there is a possible execution of sensitive USSD codes due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  13. CVE-2026-59046

    In __pkvm_guest_relinquish_to_host of mem_protect.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  14. CVE-2026-59016

    In sendAnomalyProfile of ProfilingService.java, there is a possible path traversal issue due to path traversal. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Disclosure Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  15. CVE-2026-58927

    The vulnerability is a Use-After-Free (UAF) in the EVS AIDL HAL, arising from a data race on an unsynchronized `std::weak_ptr` within `EvsEnumerator::openCamera()`. Specifically, concurrent calls from a privileged UID (e.g., `AID_AUTOMOTIVE_EVS`) can cause a torn `weak_ptr` state, leading to a virtual call through a freed object's vtable at `cameraObj->getCameraInfo(&desc)`. This allows for potential arbitrary code execution within the `hal_evs_default` process.

    Memory safety Device Google Android

    6.7 MEDIUM 0.1% exploit odds Fix listed
  16. CVE-2026-59048

    In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    5.5 MEDIUM 0.1% exploit odds Fix listed
  17. CVE-2026-59047

    In multiple locations, there is a possible denial of service due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  18. CVE-2026-59004

    In multiple locations, there is a possible permission bypass due to an uncaught exception. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Other Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  19. CVE-2026-59014

    In multiple locations, there is a possible out-of-bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  20. CVE-2026-55263

    In multiple functions of AllowBindAppWidgetActivity.java, there is a possible misunderstanding of reject/consent actions due to misleading or insufficient UI. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

    Other Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  21. CVE-2025-26433

    In multiple locations, there is a possible way to trick a user into accepting a permission due to a tapjacking/overlay attack. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

    Other Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  22. CVE-2026-49934

    In multiple functions of MmiUtils.java, there is a possible risk of USSD/MMI code execution due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

    Code execution Device Google Android

    7.8 HIGH 0.1% exploit odds Fix listed
  23. CVE-2026-59043

    In arm_lpae_split_blk_unmap of io-pgtable-arm-common.c, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    7.4 HIGH 0.1% exploit odds Fix listed
  24. CVE-2026-59005

    In insertInternal of MmsProvider.java, there is a possible multiuser isolation issue due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  25. CVE-2026-58989

    In setOemUnlockAllowedByUser of OemLockService.java, there is a possible way to bypass FRP due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  26. CVE-2026-58994

    In multiple functions of NfcService.java, there is a possible permission bypass due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  27. CVE-2026-0053

    In multiple locations, there is a possible method for a primary user to disable secure nfc on other full users due to insufficient isolation between Android users. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  28. CVE-2026-59021

    In multiple locations, there is a possible denial of service due to improper input validation. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  29. CVE-2026-59031

    In InputDispatcher::flushSensor of InputDispatcher.cpp, there is a possible denial of service due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  30. CVE-2026-59008

    In setApplicationRestrictions of DevicePolicyManagerService.java, there is a possible denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  31. CVE-2026-59010

    In deserialize of legacy.rs, there is a possible denial of service due to a missing bounds check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  32. CVE-2026-59015

    In multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Disclosure Device Google Android

    4.0 MEDIUM 0.1% exploit odds Fix listed
  33. CVE-2026-59003

    In getSubscriptionProperty of SubscriptionManagerService.java, there is a possible information disclosure due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    4.0 MEDIUM 0.1% exploit odds Fix listed
  34. CVE-2026-58926

    A Use-After-Free (UAF) vulnerability exists in the EVS HAL, allowing a privileged client to free a `buffer_handle_t` while the producer thread is still using it. This race condition, triggered via `doneWithFrame` and `setMaxFramesInFlight`, enables an attacker to manipulate freed heap memory, potentially leading to the leakage of file descriptors from the EVS HAL process.

    Memory safety Device Google Android

    2.5 LOW 0.1% exploit odds Fix listed
  35. CVE-2026-59022

    In multiple functions of MediaProvider.java, there is a possible permission bypass due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    5.5 MEDIUM 0.1% exploit odds Fix listed
  36. CVE-2026-59011

    In multiple locations, there is a possible permission bypass due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    5.5 MEDIUM 0.1% exploit odds Fix listed
  37. CVE-2026-59012

    In checkLastKnownCellIdAccessPermission of TelephonyPermissions.java, there is a possible permission bypass due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Auth & access Device Google Android

    5.5 MEDIUM 0.1% exploit odds Fix listed
  38. CVE-2026-59006

    In getTouchOcclusionMode of WindowState.java, there is a possible tapjacking issue due to a tapjacking/overlay attack. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

    Disclosure Device Google Android

    5.0 MEDIUM 0.1% exploit odds Fix listed
  39. CVE-2026-59020

    In removeUserData of DevicePolicyManagerService.java, there is a possible denial of service due to a race condition. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation.

    Denial of service Device Google Android

    5.9 MEDIUM 0.1% exploit odds Fix listed

All CVEs affecting Google Android that appear in CVE.org and NVD, sorted by how likely they are to be exploited (EPSS), with fix status and timeline.