What is the CVSS score of CVE-2026-6308?

CVE-2026-6308 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 Chrome are affected by CVE-2026-6308?

Google Chrome versions prior to 147.0.7727.101 contain an out-of-bounds read vulnerability in the media component that can enable remote code execution if users interact with malicious content.. A patch is available.

How to fix or mitigate CVE-2026-6308?

Within 24 hours: Identify all Chrome deployments across endpoints using MDM/asset management tools and confirm current version inventory. Within 7 days: Deploy Chrome 147.0.7727.101 or later via managed update mechanism (Windows Update, macOS updates, or Chrome enterprise policy); prioritize workstations with access to sensitive systems. Within 30 days: Verify 100% deployment completion through MDM reporting and conduct user awareness training on recognizing malicious web content and unexpected UI prompts.

Chrome CVE-2026-6308

EUVD-2026-23058 HIGH

Out-of-bounds Read (CWE-125)

2026-04-15 Chrome

Information Disclosure Buffer Overflow RCE Google Chrome

7.5

CVSS 3.1 · NVD

Severity by source

NVD 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

9.6 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Re-analysis Queued

Apr 17, 2026 - 15:22 vuln.today

cvss_changed

Analysis Generated

Apr 16, 2026 - 10:22 vuln.today

CVSS changed

Apr 16, 2026 - 10:22 NVD

7.5 (HIGH)

Patch released

Apr 15, 2026 - 19:46 nvd

Patch available

EUVD ID Assigned

Apr 15, 2026 - 19:45 euvd

EUVD-2026-23058

Analysis Generated

Apr 15, 2026 - 19:45 vuln.today

CVE Published

Apr 15, 2026 - 19:04 nvd

HIGH 7.5

DescriptionCVE.org

Out of bounds read in Media in Google Chrome prior to 147.0.7727.101 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

Out-of-bounds read in Google Chrome's media component (versions prior to 147.0.7727.101) enables remote code execution when attackers convince users to perform specific UI interactions on a malicious HTML page. Google rated this high severity and released Chrome 147.0.7727.101 as a fix. No active exploitation confirmed via CISA KEV at time of analysis, though CVSS 7.5 reflects significant impact if user interaction prerequisite is met. The UI gesture requirement and high attack complexity (AC:H) reduce automated exploitation risk compared to interaction-free vulnerabilities.

Technical ContextAI

This vulnerability is rooted in CWE-125 (Out-of-bounds Read) within Chrome's media processing subsystem, which handles video/audio rendering and codec operations. When parsing specially crafted media content embedded in HTML, the media component reads memory outside allocated buffer boundaries. Unlike typical buffer overflows that write beyond bounds, out-of-bounds reads can leak sensitive memory contents or trigger controlled crashes that enable code execution when combined with other exploitation techniques like heap spraying. The affected product per CPE is Google Chrome desktop versions (<147.0.7727.101) across Windows, macOS, and Linux platforms. Media subsystem vulnerabilities are particularly dangerous because web content routinely embeds video/audio, making the attack surface accessible via normal browsing. The Chromium bug tracker issue 497412658 contains technical details but access may be restricted until sufficient patch deployment occurs.

RemediationAI

Immediately update Google Chrome to version 147.0.7727.101 or later through the browser's built-in update mechanism (Settings > About Chrome) or via enterprise deployment tools for managed environments. Chrome's automatic update feature will deploy the patch within 24-48 hours for most users, but manual verification is recommended for critical systems. For environments unable to patch immediately, implement compensating controls: disable JavaScript execution for untrusted sites via browser policies (chrome://settings/content), deploy Content Security Policy headers blocking media sources from external domains, or restrict browsing to organizational allow-lists using Chrome Enterprise policy ChromeExtensionInstallBlocklist. Note these workarounds severely limit browser functionality and should be temporary. Organizations using Chromium-based browsers (Edge, Brave, Opera) should consult respective vendor advisories for equivalent patched versions. No configuration changes mitigate the vulnerability in unpatched Chrome-upgrade is the only complete remediation. Automated enterprise patch validation can query chrome://version to confirm deployment of 147.0.7727.101+.