LearnCTEM.com, Best CTEM Learning Platform
CVE Intelligence Hub

CVE-2026-58925: Google Android Use After Free Vulnerability

CVE-2026-58925 explained: high Use After Free in Google Android. CVSS 7.8. Affected versions, detection, fixes and CTEM priority.

Last updated: Nov 4, 2026

CVSS
7.8 HIGH
EPSS
0.15%
CISA KEV
Not listed
CWE
CWE-416

Sources: National Vulnerability Database, CVE.org, CISA KEV, FIRST EPSS

CVE-2026-58925 Overview

The report details a heap Use-After-Free (UAF) vulnerability within the `android.hardware.automotive.evs-default` HAL service, stemming from unsynchronized access to an `std::unordered_map`. An unprivileged application with access to the EVS manager can trigger this UAF by making concurrent calls to `setExtendedInfo` and `getExtendedInfo`, potentially enabling code execution within the privileged HAL process.

Critical Impact

Local or adjacent, authenticated attackers can exploit this Use After Free in Google Android. The CVSS base score is 7.8 (High).

Affected Products

  • Android 14.0
  • Android 15.0
  • Android 16.0
  • Android 17.0

Discovery Timeline

  • 2026-11-02: CVE-2026-58925 published to the National Vulnerability Database by security@android.com
  • 2026-11-04: last updated in the NVD database

Technical Details for CVE-2026-58925

Vulnerability Analysis

CVE-2026-58925 is a Use After Free weakness (CWE-416: Use After Free) in Google Android. Based on its CVSS vector, the flaw needs local or adjacent access, needs some level of access, and needs no user interaction. Memory is used after it was released, which can lead to code execution.

With a CVSS base score of 7.8 and an EPSS exploitation probability of 0.15 percent, apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Root Cause

The weakness is classified as CWE-416: Use After Free. Memory is used after it was released, which can lead to code execution.

Attack Vector

Based on the CVSS vector, the flaw needs local or adjacent access, needs some level of access, and needs no user interaction. Attack complexity is low complexity.

No exploitation in the wild is confirmed by CISA at the time of the last update. Check the references below for any vendor or researcher proof of concept.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Detection Methods for CVE-2026-58925

Detection Strategies

  • Inventory every instance of Google Android and compare the running version with the affected range above.
  • Check external attack surface scans for internet facing instances of the component.
  • Run an authenticated vulnerability scan once your scanner ships a check for this CVE.

Monitoring Recommendations

  • Forward Google Android application, access and audit logs to your SIEM for retrospective hunting.
  • Alert on new processes, configuration changes or outbound connections from the affected service.
  • Track the vendor advisory and the CISA KEV catalog for changes in exploitation status.

How to Mitigate CVE-2026-58925

Immediate Actions Required

  • Apply the fixed version of Google Android named in the vendor advisory.
  • Prioritize internet facing and business critical instances first.
  • Rescan after the change to confirm the exposure is closed.

Patch Information

Use the fixed version listed in the vendor advisory for Google Android. The affected ranges above show which builds remain vulnerable.

Workarounds

  • If patching must wait, restrict network access to the affected service and place it behind authentication or a web application firewall rule.

CWE References

Technical References

This entry is built directly from NVD, CISA KEV and EPSS data. Verify fixed versions in the vendor advisory before you deploy.

Frequently asked questions

CVE-2026-58925 is a high severity Use After Free in Google Android with a CVSS score of 7.8. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Related CVEs

HIGH7.5
CVE-2026-58924
Google Android

The vulnerability is a heap out-of-bounds read in the EVS HAL's `getStreamList()` method. An attacker can craft a `CameraDesc.metadata` byte array, which is parsed without validation, leading to an out-of-bounds read at an attacker-controlled offset within the HAL process's heap. The read data is then exfiltrated back to the attacker, potentially leaking sensitive information like pointers and buffer handles.

Nov 2, 2026
CRITICAL9.3
CVE-2026-118337
Google Chrome

Improper access control in Forms in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)

Oct 27, 2026
CRITICAL9.3
CVE-2026-118333
Google Chrome

Missing authorization in Video in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)

Oct 27, 2026
HIGH8.8
CVE-2026-113264
Google Chrome

Improper input validation in Extensions in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Oct 20, 2026
HIGH8.8
CVE-2026-113143
Google Chrome

Memory corruption in ANGLE in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to read memory via a crafted HTML page. (Chromium security severity: Medium)

Oct 20, 2026
HIGH8.8
CVE-2026-113137
Google Chrome

Memory corruption in Extensions in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Oct 20, 2026
All Google CVEs in 2026
Your next credential

Earn your free CTEM certification.

Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-58925 with a free CTEM certification.

Free to takePublicly verifiable

Beginner / Practitioner / Program Leader

Explore certifications