Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-13807

CVE-2026-13807: Google Chrome Use After Free Vulnerability

CVE-2026-13807 is a use after free vulnerability in Google Chrome on iOS that enables remote code execution through malicious files. This article covers the technical details, affected versions, security impact, and mitigation strategies.

Published:

CVE-2026-13807 Overview

CVE-2026-13807 is a use-after-free vulnerability [CWE-416] in the Import component of Google Chrome on iOS. The flaw affects Chrome for iOS versions prior to 150.0.7871.47. A remote attacker who convinces a user to perform specific UI gestures can execute arbitrary code by delivering a malicious file. Google classified the Chromium security severity as High. The vulnerability requires user interaction and high attack complexity, but it can compromise confidentiality, integrity, and availability once triggered.

Critical Impact

Successful exploitation allows arbitrary code execution within the Chrome iOS process, enabling attackers to run attacker-controlled code on the victim device after user interaction with a malicious file.

Affected Products

  • Google Chrome for iOS prior to 150.0.7871.47
  • Apple iPhone OS (as the underlying platform running Chrome for iOS)
  • Chromium-based Import component on iOS builds

Discovery Timeline

  • 2026-06-30 - CVE-2026-13807 published to the National Vulnerability Database (NVD)
  • 2026-07-02 - Last updated in NVD database

Technical Details for CVE-2026-13807

Vulnerability Analysis

The vulnerability is a use-after-free condition in the Import functionality of Google Chrome on iOS. Use-after-free flaws occur when a program continues to reference memory after it has been freed. An attacker who controls the freed allocation can influence the object that is later dereferenced, redirecting execution or corrupting internal state.

Exploitation requires the victim to open a malicious file and perform specific UI gestures. This user-interaction requirement raises attack complexity but does not eliminate risk, because file-based social engineering remains effective against browser users. Successful exploitation yields arbitrary code execution within the Chrome renderer or import handler scope on iOS.

The issue is tracked in the Chromium project and fixed in Chrome for iOS 150.0.7871.47. See the Chromium Issue Tracker entry for the technical reference.

Root Cause

The root cause is improper object lifetime management within the Import code path. A pointer to an object continues to be used after the underlying memory has been released. When the attacker-controlled file triggers reallocation of that memory, subsequent access dereferences attacker-influenced data. This matches the [CWE-416: Use After Free] weakness class.

Attack Vector

The attack vector is network-based delivery of a malicious file paired with user interaction. An attacker hosts or sends a crafted file that Chrome on iOS imports. The victim must perform specific UI gestures inside Chrome to trigger the vulnerable code path. No credentials are required. Once the gestures are performed, the use-after-free is reached and arbitrary code executes in the browser context.

No public proof-of-concept, exploit code, or CISA KEV listing exists for this CVE at the time of publication.

Refer to the Chromium Issue Tracker entry for additional technical detail.

Detection Methods for CVE-2026-13807

Indicators of Compromise

  • Chrome for iOS instances still reporting a version below 150.0.7871.47 in mobile device management (MDM) inventory.
  • Unexpected Chrome renderer crashes or import-related tab termination logs on managed iOS devices.
  • Delivery of unusual file types or attachments that prompt the user to import content into Chrome on iOS.

Detection Strategies

  • Query MDM and endpoint inventory sources for Chrome iOS builds and flag versions prior to 150.0.7871.47.
  • Correlate email and messaging telemetry for file lures that instruct users to open content inside Chrome on iOS.
  • Monitor web gateway logs for downloads immediately preceding Chrome crash telemetry on the same device.

Monitoring Recommendations

  • Enforce continuous version compliance checks for mobile browsers through the MDM platform.
  • Alert on repeated Chrome iOS crash reports that reference the Import component or memory faults.
  • Track user reports of unexpected UI prompts or file import behavior in Chrome on iOS.

How to Mitigate CVE-2026-13807

Immediate Actions Required

  • Update Google Chrome for iOS to version 150.0.7871.47 or later on all managed devices.
  • Push the update through MDM to enforce compliance across the mobile fleet.
  • Notify users to avoid opening unsolicited files inside Chrome on iOS until patching is confirmed.

Patch Information

Google released the fix in the Chrome Stable channel update referenced in the Google Chrome Update Announcements. Upgrading Chrome for iOS to 150.0.7871.47 or later remediates the use-after-free in the Import component.

Workarounds

  • Restrict use of Chrome for iOS until the patched version is deployed, favoring a browser without this issue.
  • Block delivery of high-risk file types at the email and web gateway to reduce lure exposure.
  • Train users to reject UI prompts that ask them to import files from untrusted sources into the browser.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.