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

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

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

Google Chrome versions prior to 148.0.7778.96 contain a sandbox escape vulnerability in the Accessibility subsystem that allows attackers with renderer process access to execute arbitrary code at…. A patch is available.

How to fix or mitigate EUVD-2026-27931?

Within 24 hours: Identify all Chrome deployments across the organization and verify current versions via inventory tools or MDM/EDR telemetry. Within 7 days: Deploy Chrome 148.0.7778.96 or later via your patch management system; prioritize user-facing systems and administrative workstations. Within 30 days: Confirm 100% deployment completion through compliance scanning and establish recurring Chrome patching cadence to enforce updates within 30 days of release.

Google Chrome EUVD-2026-27931

| CVE-2026-7914 HIGH

Access of Resource Using Incompatible Type (Type Confusion) (CWE-843)

2026-05-06 Chrome

Microsoft Information Disclosure Memory Corruption Google Red Hat Suse Chrome

8.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.3 HIGH

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

SUSE

HIGH

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 06, 2026 - 22:25 vuln.today

CVSS changed

May 06, 2026 - 22:22 NVD

8.3 (HIGH)

CVE Published

May 06, 2026 - 18:12 nvd

HIGH 8.3

DescriptionCVE.org

Type Confusion in Accessibility in Google Chrome on Windows prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Sandbox escape in Google Chrome on Windows versions prior to 148.0.7778.96 allows attackers who have already compromised the renderer process to break out of Chrome's security sandbox via type confusion in the Accessibility subsystem. The attack requires user interaction with a malicious webpage and successful renderer compromise as a prerequisite, representing a critical escalation path in multi-stage attacks. Vendor-released patch available in Chrome 148.0.7778.96. No active exploitation confirmed (not in CISA KEV), and no public exploit code identified at time of analysis.

Technical ContextAI

This vulnerability stems from CWE-843 (Type Confusion), a memory corruption class where code incorrectly assumes an object's type, allowing attackers to manipulate memory in unintended ways. The flaw resides in Chrome's Accessibility API implementation on Windows, which provides interfaces for assistive technologies. Type confusion occurs when the browser's accessibility layer misinterprets object types during inter-process communication between the sandboxed renderer and privileged browser processes. Chrome's multi-process architecture isolates untrusted web content in a sandboxed renderer process with limited system access. Accessibility features bridge this boundary to enable screen readers and other assistive tools, creating a privileged communication channel that becomes an attack surface when type safety checks fail. The CVSS vector indicates Changed scope (S:C), confirming the vulnerability enables privilege escalation beyond the renderer sandbox boundary. CPE data identifies Google Chrome on all platforms as affected, though the description specifically notes Windows as the vulnerable platform, suggesting platform-specific Accessibility API interactions.

RemediationAI

Upgrade Google Chrome on Windows to version 148.0.7778.96 or later immediately, available via Chrome's built-in updater (chrome://settings/help) or enterprise deployment channels (MSI/GPO distributions from https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html). Enterprises using managed Chrome deployments should push the update through existing software distribution mechanisms within 72 hours. For environments unable to patch immediately, implement compensating controls: disable Chrome accessibility features system-wide via Group Policy (Computer Configuration > Administrative Templates > Google > Chrome > 'Disable accessibility features'), though this breaks screen readers and assistive technologies for users requiring them - assess accessibility compliance requirements before applying. Alternatively, restrict Chrome usage to isolated virtual desktop infrastructure (VDI) environments with limited local system access, reducing sandbox escape impact. Deploy endpoint detection and response (EDR) solutions monitoring for renderer process crashes followed by unusual child process creation, which may indicate exploitation attempts. Note that disabling accessibility features may not fully mitigate risk if the vulnerable code paths are reachable through other means; patching remains the only complete remediation.