EUVD-2026-79009
GHSA-qccq-x5q5-fpjf
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 15, 2026
Let me build the JSON.
CVE-2026-58724: Android kernel use-after-free due to race condition, local EoP requiring System execution privileges, no UI. CVSS 7.0 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Reported by Google Devices. CPE: google:android. Tags: Privilege Escalation, Google, Race Condition. Reference: Android security bulletin September 2026 Pixel.
Note: "System execution privileges needed" — this is Android bulletin phrasing meaning the attacker needs System-level privileges already... Actually in Android bulletins, "System execution privileges needed" means the vulnerability requires the attacker to already have System privileges? Hmm, actually Android bulletin says "This could lead to local escalation of privilege with System execution privileges needed" — meaning the attacker needs System execution privileges? Historically it means exploitation requires the attacker to run code with System privileges already... Actually it means the vulnerability can lead to local escalation of privilege with System execution privileges needed — i.e., it requires System-level privileges to exploit. That means privilege escalation from System to... hmm, in Android, "System" is a UID (system uid 1000). So it escalates to kernel. Actually "with System execution privileges needed" means the attacker must already have System privileges. CVSS PR:L is consistent-ish. Actually PR:L. Hmm but if System privileges needed, PR:H might be more apt. Given CVSS says PR:L, I'll assess PR:L... Hmm. My own assessment: AV:L/AC:H/PR:H? Let me think. The Android phrasing "System execution privileges needed" — needed to exploit — implies significant privileges already (system UID, not just any app). That's PR:H arguably. But CVSS gives PR:L. I'll go with PR:H? Let's be careful — I should ground my assessment in the description. The description says "with System execution privileges needed" — this means the exploit requires system-level privileges. So PR:H is honest. But the vendor's own CVSS says
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from Vendor (Google_Devices) · only source for this CVE.
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
3DescriptionCVE.org
In multiple locations, there is a possible use-after-free 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.
Threat Intelligence Overview
NVD
CVE.org
EPSS
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
Exploit-DB