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

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

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

A remote code execution vulnerability in Google Chrome versions prior to 148.0.7778.216 could allow attackers to compromise employee devices through malicious websites.. A patch is available.

How to fix or mitigate EUVD-2026-33076?

Within 24 hours: Inventory all devices running Google Chrome versions prior to 148.0.7778.216 using your endpoint detection system; document the current deployment scope and affected user population. Within 7 days: Deploy Chrome 148.0.7778.216 or later to all endpoints via your managed update channels (WSUS, MDM, or equivalent). Within 30 days: Verify 95%+ adoption of the patched version, confirm no rollbacks to vulnerable builds, and document compliance in your vulnerability management system.

Google Chrome EUVD-2026-33076

| CVE-2026-9934 HIGH

Use After Free (CWE-416)

2026-05-28 Chrome

GHSA-2qvg-6g76-g2jm

RCE Denial Of Service Google Use After Free Memory Corruption

7.5

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

7.5 HIGH

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

SUSE

HIGH

qualitative

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 29, 2026 - 12:29 vuln.today

CVSS changed

May 29, 2026 - 12:22 NVD

7.5 (HIGH)

CVE Published

May 28, 2026 - 22:25 nvd

UNKNOWN (no severity yet)

CVE Published

May 28, 2026 - 22:25 nvd

HIGH 7.5

DescriptionCVE.org

Use after free in Aura in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Remote code execution in Google Chrome versions prior to 148.0.7778.216 stems from a use-after-free flaw in the Aura UI framework component. A remote attacker who lures a user to a malicious HTML page and convinces them to perform specific UI gestures can execute arbitrary code within the browser process. No public exploit identified at time of analysis, and the CVSS 7.5 score reflects high attack complexity combined with required user interaction.

Technical ContextAI

Aura is Chromium's cross-platform UI abstraction layer that handles window management, input events, and widget rendering on desktop platforms (Windows, Linux, ChromeOS). The vulnerability is classified as CWE-416 (Use After Free), a memory corruption class where an object's memory is referenced after it has been freed, allowing an attacker to manipulate the dangling pointer to redirect execution or corrupt adjacent memory. In Aura specifically, this typically occurs when UI event handlers retain references to widgets, windows, or input contexts whose lifecycle is managed elsewhere - a crafted sequence of gestures can race the object destruction logic. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering Chrome desktop builds before 148.0.7778.216.

RemediationAI

Vendor-released patch: Chrome 148.0.7778.216 - update via the browser's built-in updater (chrome://settings/help) or redeploy through enterprise management (Google Update, MDM, or package repositories) and ensure all users restart Chrome to apply the fix, per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html. Until update rollout completes, compensating controls include restricting browsing to trusted sites via enterprise URL allowlists (trade-off: breaks general web use), enabling Chrome's Site Isolation if not already on (default since Chrome 67, but verify with chrome://flags), and deploying browser-level EDR that monitors for renderer process anomalies. Disabling JavaScript via policy would block most delivery vectors but breaks the majority of modern websites and is rarely acceptable; restricting Chrome extensions and downloads will not mitigate this UI-gesture-driven flaw.