Skip to main content
VulnerabilityPublished Updated

CVE-2024-23705: Google Android · Elevation of Privilege

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Google AndroidAffected
  • =14
  • =13
  • =12
Fixed in–

AI-suggested

  1. Monitor official Google Android security bulletins closely and apply patches immediately once released for affected Android versions (12, 12L, 13, 14).
  2. Until patches are available, restrict installation of apps from untrusted sources by enforcing strict app store policies and using Mobile Device Management (MDM) solutions to control app permissions.
  3. Educate users about the risks of installing unknown or suspicious applications and the importance of cautious interaction with prompts or links.
  4. Employ endpoint detection and response (EDR) tools capable of monitoring for unusual privilege escalation attempts or suspicious local activity on Android devices.
  5. Limit local access to devices by enforcing strong authentication mechanisms such as biometrics or PINs and disable developer options or USB debugging on corporate devices.
  6. Use application sandboxing and containerization technologies to isolate sensitive corporate data and applications from potentially compromised user environments.
  7. Conduct regular security audits and vulnerability assessments on mobile device fleets to identify and remediate risky configurations or outdated software versions.

Description

In multiple locations, there is a possible failure to persist or enforce user restrictions 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.

References

Community reviews

Loading reviews…