CVE-2026-121180

Awaiting Analysis Awaiting Analysis - Queue

Buffer Overflow in Google Chrome Prior to 157.0.8103.38

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: Chrome

Description

Buffer overflow in Media in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-11-03

Last Modified

2026-11-03

Generated

2026-11-04

AI Q&A

2026-11-04

EPSS Evaluated

N/A

NVD

CVE-2026-121180

EUVD

EUVD-2026-116527

Affected Vendors & Products

Vendor	Product	Version / Range
Google	Chrome	157.0.8103.38

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 is a buffer overflow vulnerability in Google Chrome's Media component. It allows a remote attacker to execute arbitrary code inside the sandbox by tricking a user into visiting a specially crafted HTML page. The vulnerability exists in Chrome versions prior to 157.0.8103.38.

Impact Analysis

An attacker could exploit this to run malicious code on your device, potentially stealing data, installing malware, or taking control of your system. Since it requires user interaction (visiting a crafted page), the risk depends on your browsing habits and security awareness.

Mitigation Strategies

Update Google Chrome to version 157.0.8103.38 or later to address the buffer overflow vulnerability.

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

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...