Heap Buffer Overflow in Google Chrome WebCodecs

Publication date: 2026-05-28

Last updated on: 2026-05-29

Assigner: Chrome

Description

Heap buffer overflow in WebCodecs in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-28

Last Modified

2026-05-29

Generated

2026-07-09

AI Q&A

2026-05-29

EPSS Evaluated

2026-07-08

NVD

CVE-2026-9939

EUVD

EUVD-2026-33081

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 148.0.7778.216 (exc)
google	chrome	to 148.0.7778.215 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-122	A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

Executive Summary

This vulnerability is a heap buffer overflow in the WebCodecs component of Google Chrome versions prior to 148.0.7778.216. It allows a remote attacker to execute arbitrary code inside a sandbox by using a specially crafted HTML page.

Impact Analysis

The impact of this vulnerability is that a remote attacker could potentially execute arbitrary code on your system within the sandbox environment of Google Chrome. This could lead to unauthorized actions or compromise of your browser security.

Hi! I’m here to help you understand CVE-2026-9939. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70