What is the CVSS score of EUVD-2026-40493?

EUVD-2026-40493 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Google Chrome are affected by EUVD-2026-40493?

Google Chrome on iOS versions prior to 150.0.7871.47 contains a remote code execution flaw that exposes all iOS users to device compromise if they open a malicious file.. A patch is available.

How to fix or mitigate EUVD-2026-40493?

Within 24 hours: Inventory all managed iOS devices running Chrome; alert end users to avoid opening untrusted files and update their browsers immediately. Within 7 days: Deploy Chrome 150.0.7871.47 or later via MDM to all iOS devices; verify deployment completion and monitor for update failures. Within 30 days: Audit 100% compliance across all iOS Chrome installations; document remediation evidence and review mobile security policies for file-handling controls.

Google Chrome EUVD-2026-40493

| CVE-2026-13807 HIGH

Use After Free (CWE-416)

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

GHSA-vrwx-r2mm-m3qm

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

7.5

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

7.5 HIGH

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

vuln.today AI

7.5 HIGH

Network-delivered malicious file but needs a victim's specific gestures and precise heap conditions (UI:R, AC:H); no authentication (PR:N); use-after-free yields full code execution, so C/I/A all High.

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

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

SUSE

HIGH

qualitative

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 15:25 vuln.today

CVSS changed

Jul 01, 2026 - 15:22 NVD

7.5 (HIGH)

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:16 cve.org

HIGH 7.5

DescriptionCVE.org

Use after free in Import in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a malicious file. (Chromium security severity: High)

AnalysisAI

Remote code execution in Google Chrome on iOS prior to 150.0.7871.47 stems from a use-after-free in the browser's Import component, allowing a remote attacker who lures a victim into opening a malicious file and performing specific UI gestures to execute arbitrary code. Rated High by Chromium and CVSS 7.5, the flaw has no public exploit identified at time of analysis and a low EPSS of 0.24% (15th percentile), consistent with its high attack complexity and required user interaction. A vendor patch is available in the June 2026 Stable channel update.

Technical ContextAI

The vulnerability is a CWE-416 use-after-free in the 'Import' code path of Google Chrome on iOS. Use-after-free defects arise when memory is freed while a dangling pointer still references it; subsequent reuse of that memory can let an attacker control the freed object's contents and hijack execution flow, a classic route to memory corruption and arbitrary code execution in C/C++ browser engines. The affected component handles imported files, and the trigger combines processing of a malicious file with particular user-driven UI actions. Notably, Chrome on iOS is built atop Apple's WebKit rather than Blink per App Store policy, so this defect resides in Chrome's own iOS browser/import layer rather than the V8/Blink stack used on desktop builds.

RemediationAI

Vendor-released patch: update Google Chrome on iOS to version 150.0.7871.47 or later via the Apple App Store, per Google's Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); on managed fleets, push the updated Chrome build through MDM to enforce it. Until updating, the practical compensating control is user awareness: instruct users not to open untrusted or unexpected files in Chrome on iOS and to avoid following prompts to perform import/UI actions from unknown sources, since exploitation requires opening a malicious file plus specific gestures, and where feasible restrict or discourage Chrome's file-import workflow on unpatched devices. These behavioral controls do not fully eliminate risk, so upgrading to the fixed build is the only durable remediation.