CVE-2026-2650
Received Received - Intake

Heap Buffer Overflow in Google Chrome Media Component

Publication date: 2026-02-18

Last updated on: 2026-02-19

Assigner: Chrome

Description
Heap buffer overflow in Media in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-02-18
Last Modified
2026-02-19
Generated
2026-07-06
AI Q&A
2026-02-19
EPSS Evaluated
2026-07-05
NVD
CVE-2026-2650
EUVD
EUVD-2026-7941

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 145.0.7632.109 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a heap buffer overflow in the Media component of Google Chrome versions prior to 145.0.7632.109. It allows a remote attacker to potentially exploit heap corruption by using a specially crafted HTML page.

Impact Analysis

The vulnerability could allow a remote attacker to cause heap corruption, which might lead to unexpected behavior such as crashes or potentially allow execution of arbitrary code within the context of the browser.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2650. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart