Heap Buffer Overflow in Google Chrome WebRTC

Publication date: 2026-05-20

Last updated on: 2026-05-21

Assigner: Chrome

Description

Heap buffer overflow in WebRTC in Google Chrome on prior to 148.0.7778.179 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-20

Last Modified

2026-05-21

Generated

2026-06-30

AI Q&A

2026-05-20

EPSS Evaluated

2026-06-28

NVD

CVE-2026-9119

EUVD

EUVD-2026-31167

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 148.0.7778.178 (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 WebRTC component of Google Chrome versions prior to 148.0.7778.179. It allows a remote attacker to execute arbitrary code within a sandboxed environment by tricking a user into visiting a specially crafted HTML page.

Impact Analysis

Exploitation of this vulnerability can lead to remote code execution with high impact on confidentiality, integrity, and availability. An attacker could run malicious code inside the browser's sandbox, potentially compromising sensitive data, altering information, or disrupting services.

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

0/70