CVE-2026-58716

Received Received - Intake

Race Condition in Android System Leads to Privilege Escalation

Publication date: 2026-09-15

Last updated on: 2026-09-18

Assigner: Google Devices

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-15

Last Modified

2026-09-18

Generated

2026-10-06

AI Q&A

2026-09-16

EPSS Evaluated

2026-10-05

NVD

CVE-2026-58716

EUVD

EUVD-2026-79006

Affected Vendors & Products

Vendor	Product	Version / Range
google	android	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
CWE-367	The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

Attack-Flow Graph

Executive Summary

This vulnerability is a race condition where a time-of-check to time-of-use issue allows local privilege escalation. An attacker could exploit this to gain higher system privileges without needing user interaction.

Impact Analysis

If exploited, this vulnerability could allow an attacker to gain elevated system privileges on your device. This might let them install malicious software, access sensitive data, or perform unauthorized actions.

Compliance Impact

This vulnerability involves a race condition leading to local privilege escalation, which could allow unauthorized access to sensitive system functions. Such access may compromise data confidentiality and integrity, potentially violating compliance requirements under GDPR (data protection) and HIPAA (health data security).

Mitigation Strategies

Apply security patches or updates from the vendor if available. Monitor vendor advisories for fixes. Restrict user privileges to minimize potential impact. Implement additional monitoring for unusual system behavior.

Hi! I’m here to help you understand CVE-2026-58716. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70