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

EUVD-2026-35230 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.1%.

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

Google Chrome versions prior to 149.0.7827.103 contain a HIGH-severity heap corruption vulnerability in the File Input component that can be exploited when users visit a malicious webpage; no public…. A patch is available.

How to fix or mitigate EUVD-2026-35230?

Within 24 hours: Issue security alert to all users; audit current Chrome versions across the desktop fleet to identify unpatched systems. Within 7 days: Deploy Chrome 149.0.7827.103 or later to all endpoints; enforce mandatory updates through Group Policy or equivalent mobile device management controls. Within 30 days: Verify patch compliance across 100% of Chrome installations; enable auto-update policies to prevent future version drift.

Google Chrome EUVD-2026-35230

| CVE-2026-11630 HIGH

Use After Free (CWE-416)

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

GHSA-72h3-r85p-88m3

Denial Of Service Use After Free Memory Corruption Google

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

SUSE

CRITICAL

qualitative

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 09, 2026 - 11:22 vuln.today

CVSS changed

Jun 09, 2026 - 11:22 NVD

8.8 (HIGH)

CVE Published

Jun 09, 2026 - 00:16 nvd

UNKNOWN (no severity yet)

CVE Published

Jun 09, 2026 - 00:16 nvd

HIGH 8.8

DescriptionCVE.org

Use after free in File Input in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

AnalysisAI

Heap corruption in Google Chrome's File Input component before version 149.0.7827.103 allows a remote attacker to exploit a use-after-free condition by luring a user to a crafted HTML page, with Chromium rating the issue Critical. No public exploit identified at time of analysis, but the high CVSS 8.8 score and browser attack surface make this a priority patch for desktop fleets.

Technical ContextAI

The flaw resides in Chrome's File Input handling, the rendering-engine component responsible for processing <input type="file"> elements and associated file-picker interactions. Classified as CWE-416 (Use After Free), the root cause is a dangling pointer to a heap object that has already been freed; subsequent dereferences let an attacker manipulate the freed allocation to corrupt heap metadata or hijack control flow. In Chromium's sandboxed renderer process, such bugs are commonly chained with a sandbox escape to achieve full code execution outside the browser, but on their own they can still leak data or crash the process.

RemediationAI

Vendor-released patch: Google Chrome 149.0.7827.103 (Stable channel) - upgrade all desktop installations immediately via the built-in updater or managed deployment tooling, then force a browser restart so the new binaries are loaded. Validate the rollout against the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html and verify downstream Chromium-based browsers (Edge, Brave, Opera, Vivaldi) have absorbed the fix before considering remediation complete. As a compensating control until patching completes, restrict browsing to trusted sites via enterprise URL allowlists or proxy filtering, and consider temporarily disabling file upload workflows on untrusted origins through site-permission policies - note the trade-off that this breaks legitimate file-upload features on web apps. Avoid relying on the site-isolation sandbox alone, since a UAF in the renderer can be chained with a separate sandbox escape.