What is the CVSS score of CVE-2026-13885?

CVE-2026-13885 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of Google Chrome are affected by CVE-2026-13885?

Google Chrome for Android (versions before 150.0.7871.47) contains a use-after-free vulnerability in the graphics renderer that enables remote code execution when users visit compromised websites.. A patch is available.

How to fix or mitigate CVE-2026-13885?

Within 24 hours: Verify Chrome for Android auto-update status in MDM; run inventory scan for devices on versions prior to 150.0.7871.47. Within 7 days: Enforce Chrome for Android update to version 150.0.7871.47 or later across all managed devices; escalate non-compliant devices to device owners. Within 30 days: Complete patching audit and document remediation; send targeted user guidance about avoiding untrusted websites.

Google Chrome CVE-2026-13885

EUVD-2026-40571 HIGH

Use After Free (CWE-416)

2026-06-30 chrome-cve-admin@google.com

GHSA-vgmm-5q8c-x2qh

RCE Denial Of Service Google Use After Free Memory Corruption Red Hat Suse

8.8

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

8.8 HIGH

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

vuln.today AI

8.8 HIGH

Remote crafted page needs no privileges but requires the user to visit it (UI:R); renderer memory-corruption RCE gives high C/I/A within an unchanged sandbox scope.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

HIGH

qualitative

Red Hat

8.8 MEDIUM

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 14:26 vuln.today

CVSS changed

Jul 01, 2026 - 14:22 NVD

8.8 (HIGH)

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:17 cve.org

HIGH 8.8

DescriptionCVE.org

Use after free in Skia in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Sandboxed remote code execution in Google Chrome for Android before 150.0.7871.47, stemming from a use-after-free in the Skia graphics library, lets a remote attacker run arbitrary code within the renderer sandbox by luring a victim to a crafted HTML page. Google rated the Chromium security severity as Medium, and no public exploit has been identified at time of analysis; the EPSS score is low (0.26%, 17th percentile), and the bug is not on CISA KEV. Exploitation requires user interaction (visiting the malicious page) but no authentication.

Technical ContextAI

The flaw lives in Skia, Chromium's open-source 2D graphics rendering engine that backs canvas, SVG, and general page compositing on Android. The root cause is CWE-416 (Use After Free): Skia continues to reference a heap object after it has been freed, allowing an attacker who controls rendering input to reclaim that memory and steer execution. Per the EUVD/NVD CPE data the affected component is Google Chrome for Android at versions below 150.0.7871.47; because Skia executes inside the renderer process, successful exploitation yields code execution constrained to the Chromium sandbox (CVSS scope Unchanged, S:U) rather than full host compromise absent a separate sandbox-escape bug.

RemediationAI

Vendor-released patch: update Google Chrome for Android to 150.0.7871.47 or later via the Google Play Store or Chrome's built-in updater, then relaunch the browser to complete the update; this is the primary and sufficient fix (see https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). In managed environments, push the update through mobile device management to enforce the minimum version. As an interim compensating control before patching, avoid opening untrusted links and restrict high-risk browsing; note that fully disabling GPU/graphics acceleration is not reliably exposed on Android Chrome and would not cleanly remove Skia's software rendering path, so it is not a dependable workaround - prioritize the version upgrade instead.