CVE-20XX-?
agent?

Google Android CVEs.

Published CVEs affecting Google Android, ranked by exploit odds.

5 CVEs · updated 2026-11-19 04:08 UTC

Reset all
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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.