CVE-2026-58716

Time-of-check to time-of-use race condition enables local privilege escalation in Android

Published Sep 15, 2026 CVSS 3.1 · 6.7 Medium EPSS < 1% KEV · Not listed
Description
In multiple locations, there is a possible time-of-check to time-of-use due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

Analysis

AI-generated

Technical impact

A race condition exists in multiple locations within the Android system where a check is performed on a resource and the resource is used before the check can finish, creating a time‑of‑check to time‑of‑use flaw. This flaw can allow a local attacker to execute code with system‑level privileges. The affected component grants System execution rights, so exploitation could compromise the entire device, allowing the attacker to install malware, exfiltrate data, or modify system settings, thereby impacting confidentiality, integrity, and availability.

Affected Systems

The vulnerability affects Google Android devices, with Google identified as the CNA. All Android systems containing the unpatched race condition are considered at risk.

Risk and Exploitability

The CVSS score of 6.7 indicates a medium-to-high risk severity. The EPSS score is <1% and the vulnerability is not listed in the KEV catalog, suggesting that it is not yet widely exploited, but local exploitation does not require user interaction. The attack can be carried out from a local user context, so any device user or local process can trigger it. Given the potential for full system compromise, the risk warrants timely remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the Android security patch released by Google that addresses the race condition and ensures that the affected checks and usages are properly synchronized.
  • Reboot the device after installing the patch to load the updated code and clear any cached state that could still trigger the race.
  • Ensure that SELinux is in enforcing mode after the patch; disable permissive mode if it is enabled to limit privilege escalation attempts.

Generated by OpenCVE AI on September 20, 2026 at 13:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Time-of-check to time-of-use race condition enables local privilege escalation in Android
Type Values Removed Values Added
CPEs cpe:2.3:o:google:android:-:*:*:*:*:*:*:*
Type Values Removed Values Added
Title Local Privilege Escalation via Time‑of‑Check to Time‑of‑Use Race Condition in Android
Type Values Removed Values Added
Title Local Privilege Escalation via Time‑of‑Check to Time‑of‑Use Race Condition in Android
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Google
Google android
Weaknesses CWE-362
CWE-367
Vendors & Products Google
Google android
Metrics cvssV3_1

{'score': 6.7, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Description In multiple locations, there is a possible time-of-check to time-of-use due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
References
Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition

Sources

Status
PUBLISHED
Assigner
Google_Devices
Published
Updated
Sep 16, 2026, 3:57 AM
Reserved
Jul 2, 2026, 5:39 AM
Status
Analyzed
Published
Sep 15, 2026, 7:17 PM
Modified
Sep 18, 2026, 1:05 PM