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

EUVD-2026-28071 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-28071?

Google Chrome versions prior to 148.0.7778.96 contain a high-severity remote code execution vulnerability in the ReadingMode component that allows attackers with renderer process access to bypass…. A patch is available.

How to fix or mitigate EUVD-2026-28071?

Within 24 hours: Inventory Chrome deployments and identify systems running versions prior to 148.0.7778.96. Within 7 days: Deploy Chrome 148.0.7778.96 or later via your patch management system across all endpoints; prioritize high-risk users (finance, legal, executive). Within 30 days: Audit browser isolation policies and renderer sandbox configurations; consider Windows Defender Application Guard or similar containment for high-risk user populations.

Google Chrome EUVD-2026-28071

| CVE-2026-7984 HIGH

Use After Free (CWE-416)

2026-05-06 Chrome

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

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

SUSE

HIGH

qualitative

Red Hat

9.0 MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

May 06, 2026 - 22:33 vuln.today

CVSS changed

May 06, 2026 - 22:22 NVD

8.8 (HIGH)

CVE Published

May 06, 2026 - 18:13 nvd

HIGH 8.8

DescriptionCVE.org

Use after free in ReadingMode in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Remote code execution in Google Chrome's ReadingMode component (versions prior to 148.0.7778.96) allows attackers who have already compromised the renderer process to escape sandbox restrictions and execute arbitrary code on the underlying system. The vulnerability requires user interaction to visit a malicious webpage but exploitation complexity is low once renderer compromise is achieved. EPSS data not available; no CISA KEV listing identified at time of analysis, indicating no confirmed widespread exploitation. Vendor-released patch available in Chrome 148.0.7778.96.

Technical ContextAI

This use-after-free (CWE-416) vulnerability exists in Chrome's ReadingMode feature, which provides simplified article views for web content. Use-after-free conditions occur when memory is accessed after being deallocated, creating opportunities for memory corruption attacks. The affected CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) indicates all Chrome installations below version 148.0.7778.96 are vulnerable. The vulnerability specifically targets the ReadingMode parsing or rendering logic, where improper object lifecycle management allows a freed memory reference to persist. Critically, this requires prior renderer process compromise, meaning the attacker must first exploit another vulnerability or social engineering to gain code execution within Chrome's sandboxed renderer before leveraging this flaw for sandbox escape.

RemediationAI

Update Google Chrome to version 148.0.7778.96 or later immediately via the browser's built-in update mechanism (Settings → About Chrome) or enterprise deployment tools. The vendor advisory at chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html confirms patch availability. For environments unable to patch immediately, compensating controls include disabling ReadingMode feature via Chrome enterprise policy (ReadingModeEnabled set to false) which eliminates the vulnerable code path but removes legitimate functionality for users who rely on simplified article views. Additional defense-in-depth measures include restricting Chrome extensions to enterprise-approved lists (reducing renderer compromise vectors), enabling Site Isolation via chrome://flags to strengthen sandbox boundaries, and deploying endpoint detection systems to monitor for suspicious renderer process behavior. Note that disabling ReadingMode does not protect against the prerequisite renderer compromise that attackers would still attempt via other vulnerabilities.